Issue with "New Project" button in Portfolio Planning Workspace. No pm_project generated.

[Nicol_s2]

I'm encountering an issue when creating a new project from the Portfolio Planning Workspace.

When I click the "New Project" button, it generates a record in the sn_align_core_project table, but no corresponding record is created in pm_project.

I already have an Alignment Integration set up from pm_project to sn_align_core_project, and that direction works fine. However, the reverse, from sn_align_core_project to pm_project, does not seem to work.

How can I make sure that a record is also created in pm_ project when using the "New Project" button in the Portfolio Planning Workspace? If there's no straightforward solution to this, I’d prefer to disable or hide the button to prevent confusion.

Thanks!

[phil_bool_unifi]

This is a core function that you shouldn't have to configure, but I noticed that I have some mandatory fields on the Project table that needed to be set before creation was successful.  For me, it was the date fields.  By setting the Approved start/end dates on the new Project Planning Item, I could get an (otherwise OOB) instance to create a Project when I created a planning item.  Have a look and see what mandatory fields you have on the Project record, and consider making them mandatory on the project planning item form.
If that isn't the case for you, and you're still having trouble, it might help to know that the action to synch data from "alignment to execution" (meaning from the planning items back to the real project table) requires the 'Execution System' field to be set when the planning item gets created.  You can see the conditions by looking at the 'Sync Data from Alignment to Execution' business rule on the sn_align_core_planning_item table.  Have a look at your project planning item in a list to see if it got that value set.  If not, check if you've got any custom business rules on insert for that table.

[Nicol_s2 · Accepted solution]

Hello,

While this wasn’t exactly my issue, your input pointed me in the right direction.

The root cause turned out to be a mismatch in the State values between the two tables which caused an unexpected error in this Business Rule: Validate state mapped to bucket.

Once that was corrected, everything started working as expected.

Thanks again for your help.

Best regards.

[phil_bool_unifi]

I'm glad that helped.  Definitely a good reminder to everyone that the 'State' field is a lot more than just a choice field, and customisation of it isn't to be taken lightly 🙂