Default % Allocation and Role MSP Mapping with PPM
search cancel

Default % Allocation and Role MSP Mapping with PPM


Article ID: 110700


Updated On:


Clarity PPM SaaS Clarity PPM On Premise


When saving a project plan from Microsoft Project (MSP) to CA Project & Portfolio Management (PPM), any newly added or updated Team member from the Resource Sheet has their Default Allocation (DA) % updated in CA PPM to 100% and the Project Role field value becomes null.


Component: PPMMSP


Solution 1: For new resources added to the project or resources updated in MSP, this would be by design. This data is reliant upon data populated in a reserved field (Text3) at the Resource Sheet level (both Default Allocation and Role are populated based on the values set on the Team tab for these fields in PPM, and when the project is then exported from PPM to MSP, that information is populated and stored in the Text3 field for that Resource. So, the project would have to be saved back to PPM, populate the role and Default allocation in PPM, then export the project to MSP. At that point the Default Allocation and Role for the resource should stay. 

For any updated team members, check to make sure that the following fields aren't updated: 
  • Resource Name
  • Initials
  • Text3
  • Text5
  • Email
These are reserved fields and as referenced in the documentation for Resource, Allocation and Field Mapping, changing any of these fields can adversely affect version control, project saving and reporting. 

Solution 2: If the above does not help, also check to make sure you are on a supported Microsoft Project version for the MSP Interface type (Legacy or New Driver) and version. For a list of supported updates with the MSP New Driver for CA PPM 14.4 and higher, see: KB000011553

Additional Information

Reference KB000071385 - CA PPM and MSP integration - List of Knowledge Documents
Reference KB000015956 - CA PPM and MSP integration known defects - Support Technical Document Index