Invalid Project Summary Task Constraint In MSP when Using the New Driver

Article Id: 130911
Status: Published
Updated On: 18-04-2019 15:40
Products:
CLARITY PPM FOR ITG , Clarity PPM On Premise , CLARITY PPM FEDERAL , Clarity PPM SaaS , Clarity PPM SaaS - Application , Clarity PPM SaaS - Application , Clarity PPM On Premise
Issue/Introduction:



The project summary task (task 0) of  project has an invalid 'Start No Earlier' constraint, which then prevents the project from opening correctly when launched from PPM Clarity to Microsoft Project. Every time the project is launched to MSP, a message regarding the constraint is thrown:

"This action will cause a scheduling conflict for summary task 0 <task name>. To remove the constraint on the summary task, click OK. To undo the action that caused the conflict, click Cancel."

Clicking on OK does remove the constraint, but the message reappears any of the following times the project is launched to MSP, even if the project is saved back to PPM without a constraint. 

The Project Summary Task shound not have a constraint, so the expected value for the constraint is NA. 

How do we get the constraint of NA to permanently remain on the project summary task? 

Environment:

Release: CODFSS99000-15.4-PPM SAAS FedRAMP-Sandbox-Small Environment
Component:

Resolution:

Run the below query to temporarily remove the project from the prdocument table. This will create a backup of the original file in case it's needed for any reason. (For On Demand customers, please open a case to have this resolved):

IMPORTANT: IMPACT OF RUNNING SCRIPT:

  • Any custom field data not mapped to PPM will be deleted from the project. This only impacts data entered in a MSP Field (such as a text field) and that data isn't stored in PPM. This impacts both the MSP New Driver and MSP Legacy Driver.
  • MSP New Driver: All Fixed Work tasks will currently change to Fixed Units.  The user will need to manually change all applicable tasks back to Fixed Work the next time the project is opened in MSP.
Run the below query:

update prdocument

set prrecordid = ?? where prrecordid=?

and prtablename= 'PRJ_PROJECTS'

Notes:

1. Replace the ? with the 5 million number of the project. For ?? change the 5 to a 9. This will create a backup of the record in the database.

2. Run the below query to ensure that there is not already a project with the ?? prrecordid:

        select * from prdocument where prrecordid = ??

3. To find the 5 million number for the project, you can run the below query (or it can be found in the PPM URL when clicking on the link to the project from the project list) 

 select id from inv_investments where name='<project name>' and object_type = 'PROJECT'