Avoidance: Use the supported method of copying and pasting of tasks in MSP when working with CA PPM documented at: KB000010395
Option 1: Run the below query to temporarily remove the project from the prdocument table. (For On Demand/SaaS customers, please open a case to have this done):
IMPORTANT: IMPACT OF RUNNING SCRIPT:
- MSP Legacy Driver: All custom views for the project will be deleted
- When the project is opened from PPM after the update, the project will only open with the default columns set for the view.
- Users will have to recreate their views for the project, unless they have them saved in MSP. (This doesn't apply in the new driver, as views are no longer saved. Users should always save the views on their MSP and switch to that view after the project opens).
- 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:
set prrecordid = ?? where prrecordid=?
and prtablename= 'PRJ_PROJECTS'
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'
Option 2: Downgrade to the Microsoft Project February 2016 update as this issue is not reproducible there.
- While this update is supported in 14.x and higher, downgrading to this update causes risks of other issues that Microsoft has fixed in updates higher then February 2016, so downgrading should be used with caution and only after testing for any side effects.
- For details on supported MSP Updates with CA PPM, see KB000011553