MSP Error "Save Failed" if project has subproject

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

When you try to save a project with a sub project from Microsoft Project (MSP) back to Clarity, a MSP "Save Failed" error is generated. 

Checking the app-ca.logs, the following warning displays: 

WARN 2019-10-07 15:43:16,617 [http-nio-14001-exec-488] niku.schedulers (clarity:unknown:none:schedulers.postProject) ImportProjectProcessor.setProjectRecords(): Insufficient right to add/modify project record

Environment

Release : All

Component : CLARITY SAAS MICROSOFT PROJECT (MSP)

Cause

This is due to missing edit rights to the sub project. 

Resolution

Grant the user Project - Edit rights to the sub project. This can be done via instance level access using the below steps:

1. In Classic Clarity go to Administration->Resources
2. Click on the impacted user
3. Click on the Resource's Access Rights drop down, then select Instance
4. Click 'Add'
5. For Object, select Project
6. Click Next
7. Filter on project*edit* in access rights and click the check box next to Project - Edit (Or Project - Edit Management) and click Add and Continue
8. Filter for the sub project, and then select the check box next to the project
9. Click Add

Additional Information

• If the above doesn't help, see also: MSP Error: 'Project Save Failed' - master KB
• See MSP Integration - Master KB of Known Issues
• See MSP Integration Known Defects - Master KB