Alignment integration not creating demand records

[Luke Wilkins]

I'm using a domain separated instance on Rome and have the SPM std licence. I have the following issue:

In a test environment i have set up Alignment Planner Workspace:

• I'm using the OOTB Project Portfolio Management planning hierarchy (global domain)
• I've created a Planning organisation (ACME domain)
• I've created the ServiceNow internal integration for the OOTB Project Portfolio Management planning hierarchy (global domain)

If i create a new demand in dmn_demand (assuming i have provided the planning organisation) the integration creates the linked record in sn_align_core_demand correctly

If i create a new demand in the alignment planner workspace, i see the record in sn_align_core_demand but no record is created in dmn_demand. The integration errors list provides a message of : The request cannot be processed - null

To add to my frustrations, i have this working correctly in a (dom sep) Dev instance (also Rome) but the same issues are happening in a (dom sep) Sandbox instance (Tokyo).

I've run through the flow executions and it seems to be failing at the point of inserting the record into the dmn_demand table but i can't see any differences comparing the rest of the flow with the working dev instance.

Can anyone think what i have missed or configured incorrectly?

[Saurav11]

hello,

Is there any BR which may been causing the issue. Did you try the script tracer and see what BR's are running. see if there is any difference in the BR on change in BR which may be causing the abort action of demand while inserting.

Please mark my answer as correct based on Impact.

[Luke Wilkins]

Thanks but it doesn't look like that's the case. The tracer showed no errors and the BRs running are the same in the instances where it's working correctly - no updates to the ootb BRs either. Thanks for the tip on the tracer though!

[Saurav11]

Hello,

Did that Br or script include run which actually inserts the demand along with all the lines?

[Luke Wilkins]

Running the tracer in Dev environment (where the demand creation works correctly), shows exactly the same BRs running as it shows in Test environment.

It's the 'Update or insert - execution records' step in the 'Sync data from alignment to execution' subflow that seems to be failing: