Issue
You are seeing Duplicate Expense Lines being created when the "glide.cost_mgmt.process_task_top_task" System Property is set to true.
There is one Expense Line on the Project Task. Then there is another duplicate Expense Line which is on the 'Top Task' Project.
Example:
- You create an Expense Line on PRJTASK0001 which has Top Task = PRJ00002
- You then see that PRJ00002 has an Expense Line with duplicate values but the Expense Line 'Number' is different.
Cause
This is the expected System Behaviour when the "glide.cost_mgmt.process_task_top_task" System Property is set to true.
Resolution
If you would like all Expense Lines to be visible from the 'Top Task' Project
- To achieve this, you should enable the "glide.cost_mgmt.process_task_top_task" System Property.
- Please be aware that there will now be two Expense Lines created when you are adding an Expense Line on your Project Tasks.
- One will be created on the Project Task. The other will be created on the Project.
- The Project 'Actual cost' Value will remain correct even though there is now two Expense Lines.
- You may also want to ensure that your Expense Lines Related List on the Project Form is now only retrieving Expense Lines with the following query:
- Expense Line.Task = Project Number (Example; Expense Line.Task = PRJ00002)
- This should be the default Out Of Box configuration for this Related List
If you do not want the above behaviour. Then you should be sure to set the "glide.cost_mgmt.process_task_top_task" System Property to false.
- You may want to consider setting the "com.snc.project.rollup.cost" System Property to true in this scenario.
- This will mean that the Actual cost is now calculated on every Project Task as well as the Project and it will be visible from each sub-level.
- This will mean that there are no duplicate Expense Lines being created. However, please be aware that you will not be able to see the Project Task Expense Lines on the main Project when using this configuration.
- Instead you will need to go to each Project Task to find the related Expense Lines.
- As a workaround for this, you can add a Defined Related List to the Project Form that is querying the Expense Line Table for the following:
- Task.Top Task = Project Number (Example; Task.Top Task = PRJ00002)
