
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2019 08:18 AM
Hi,
I've had to fiddle around with the project form to accomodate a new business process that is due to come in. Everything has gone OK and I've been able to make the form do what I need it to do. However, when I create a new Project Task, I get two different error messages.
If the parent project is set to Manual calculation, the error message reads:
Error: PRJXXXXXXX can not be the New Parent to <sub_task name>
Invalid Insert
If the parent project is set to Automatic calculation, the error message reads:
Auto Projects can not change calculation
Invalid Insert
In both cases, the project task is inserted and everything appears to work OK from then on but I want to find out why this is happening.
Most of the changes I have made involve removing fields particularly project date fields. I added them back and made them invisible on the form in case they were needed for something in the backend but issue still exists.
Can anyone help?
Ideally we could dispose of auto and manual calculation and simply force one or the other but this area is so complicated!!!
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2019 09:47 AM
These errors are handled in OOB business rule.
Error: PRJXXXXXXX can not be the New Parent to <sub_task name>
--> This is handled in business rule "Validate change parent".
Auto Projects can not change calculation
--> This is handled in business rule "ProjectWorkbenchPhaseValidationAndUpdate"
Both of these errors occurs when project and project task calculation doesn't match.
You should set project calculation to manual to get rid of these errors.
Regards,
Sachin

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-31-2023 01:30 AM
Hi Nihar - Sorry but it was a long time ago and I don't have access to the instance that I was working on back then. I asked an ex-colleague to take a look and the business rule that generates the message is not active on that instance ("Validate Change Parent").
It seems that my solution back then was simply to disable the business rule. I'm not sure what impact that has in the long run but that company has been using PPM for 4 years with no known issues.
I know that solution isn't perfect. If I hit the same problem now I'd definitely spend more time looking at the underlying cause. Sorry.
If you solve it can you post here please? It would be interesting to know what caused it.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-31-2023 01:35 AM
Did you see this KB article on the subject:
Getting error as "Error: "Project Number" can not be the new parent to child" when users trying to c...

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-10-2019 04:07 AM
Thank you. Pointed me in right direction.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2019 03:04 AM
Hello,
Both my parent and my child are set to "Automatic" calculation and so the error shouldn't be invoked.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-21-2022 10:28 AM
hello,
did you find the solution to this? It also generates that error when it has the same calculation