Microsoft Project (MSP) Assignment Units changes are not being reflected after saving a project back to Clarity and reopening the project. The value reverts back to the Resource's Allocation on the Project's Team tab.
Steps to Reproduce:
Expected Results: Units remains at 50%
Actual Results: Units have reverted back to 100% which is the allocation assigned to the resource on the Team tab
Release: All Supported
Component: Microsoft Project Interface
This is working as designed if 'MSP Assignment Units Mapping with Clarity Assignment Max % Load' is unchecked in Clarity. MSP Assignment Units changes are sent to the 'Max % Load' field in Clarity for the assignment. However, if the setting 'MSP Assignment Units Mapping with Clarity Assignment Max % Load' is not checked, when the project is exported from MSP to Clarity, it will export the assignment units from the Resource's allocation on the Team tab.
To export the assignment's allocation from the Max % Load field, check the following setting: 'MSP Assignment Units Mapping with Clarity Assignment Max % Load'. This will then cause all tasks assignments to be pulled from the 'Max % Load' field instead of the resource's allocation on the project.
Note: This setting works for all loading patterns in the MSP New Driver, but only with the Uniform loading pattern setting in the MSP Legacy Driver
Important: It is recommended to test this out before making this change to see if there is any impact based on your MSP/Clarity configurations. It can impact how ETCs/Actuals are calculated.