Using various filters in your project template helps with managing project tasks by setting clear bounds on specific data inputs. The limit rows filter restricts the amount of data entries returned, making tracking and adjusting key more straightforward.
This article will explain the steps on how to build the a template using limit rows and examples on how the data will be returned.
The binding element for Limit Rows
You can use the limit rows filter on Actions, Decisions, Impacts, Schedule Tasks, Benefits and Ongoing Costs by using the following binding element: [Rows(number of rows)]
Building the Template
Now let's look at how to build a table that uses the Limit Rows filter.
Example, you want to filter the amount of rows to return only 4 key milestones that are currently in "Not Started and In Progress" status on your schedule plan, you can do so by using the following syntax: {@Schedule}[^TaskType=Milestone&&Status=Not Started, In Progress][Rows(4)]
The first cell will contain the syntax mentioned above which is used to filter the amount of rows (as shown in image below) and the rest of the columns in the table include the binding elements that will be used to retrieve the impact data.
For more on the different impact binding elements, please refer to the overall How to Build Project Templates article.
The table in the template will be structured as follows:
When exported, the report will look as follows with the milestones:
Below attached is an example template that has been created to filter impacts using the Limit Rows filter.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article