To create a schedule task table, add a table to your Word or PowerPoint template with {@Schedule} in the first cell, and Fluid will generate one row per schedule task when the report is exported.
Rules
Use a table with a header row. The first cell of the header row must start with {@Schedule}.
The next row defines the columns. Use the property binding elements below — no Schedule. prefix needed inside the table.
Common properties
Property | Binding Element |
Title | {Title} |
Task Type | {TaskType} |
Start Date | {StartDate} |
End Date | {DueDate} |
Status | {Status} |
% Complete | {PercentComplete} |
Current RAG | {Rag} |
Latest Strapline | {Strapline} |
Assignees | {Owner.Name} |
Custom Property | {ExtProps.CustomPropertyName} |
You can find more schedule binding elements by clicking here.
Examples on how to build the templates
Basic schedule table
{@Schedule} | |||
{Title} | {StartDate} | {DueDate} | {Status} |
Returns every schedule task, one per row.
Filtered by Task Type
Using the task type "Milestone" as an example, the table can be built in the following way to export the schedule milestones.
{@Schedule}[^TaskType=Milestone] | |||
{Title} | {StartDate} | {DueDate} | {Status} |
Returns only tasks of type Milestone.
Additional Filters by Task Type
Using additional filter options, you can consolidate different task types and expand the filter to sort the tasks by due date while restricting the table to return a specified number of rows. For example, the following query exports 6 phases and milestones sorted in ascending order by due date.
{@Schedule}[^TaskType=Phase, Milestone][SORTBY(DueDate Asc)][Rows(6)] | |||
{Title} | {StartDate} | {DueDate} | {Status} |