AW - Document Publisher - Entities Relation

could you give a little more detail on what you are looking to achieve ?

Hi Jim,

Thanks for you answer, sure.

What I want to achieve is to run the template on the project and be able to show in the report the resources associated with the activities of a specific milestone. Additionally, I want to be able to filter the resources by an attribute (custom field) called resource type that has two options: Internal and External.

The Entities and Fields involved are:
- Entity where the Report is executed: Project
- Field 1: Schedule Milestone with name "Project Charter"
Entity 1: Milestone
- Field 2: Schedule Activity 1 that is a child of the "Project Charter" milestone:
Entity 2: Task
- Field 3: Schedule Activity 2 that is a child of the "Project Charter" milestone:
Entity 3: Task
- Field n: Schedule Activity n that is a child of the "Project Charter" milestone:
Entity n: Task
- Field 4: Resource Name
Entity 4: Resource
- Field 5: Resource Type
Entity 5: User
- Field 6: RemainingEffort
Entity: Workitem

With the above I want to show in a table that shows me in column 1 the resource type and in column 2 the Total RemainingEffort of Internal Resources

Regards,

To complement, I leave you the script that I am working with in the template that has only allowed me to show the data at the milestone level:

[ !field=Project.WorkItemHierarchyLink !relationfield=Parent !filterfield=Child.Name !filteroperator=Equal !filtervalue=”Project Charter” !totalrow=False ]

You can embed tables within tables but im not sure youll get the exact results you are looking for and it will be slow to render the doc.   I would suggest creating custom text fields on the milestone to capture the Internal and external resources names.  Then workflows that update these fields if resources on the children tasks of the relevant MS are updated.  this way you are just pulling MS meta data into doc publisher and dont have to worry about filtering etc

ie 

when resource assignment is made to a task,  the workflow checks if there is a parent MS, if the parent MS is the right name (i dont recommend using name as they can easily be changed….MS type would be better)  if yes to those conditions update the new MS field with the resource name.   You would need a deletion version and consider resource state etc as well