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]

Do you see any difference in the subflow "Update or insert - execution records" in Dev and test. Do you see anyone recently changes or updated anything?

[Luke Wilkins]

No, i've been through the subflows in both environments. The only difference is that step 7 returns has_any_error=TRUE in test, but returns FALSE in Dev.

There are no updates to the flows by anyone (i installed APW and the integrations plugin only recently in both environments)

[Farfara]

@Luke Wilkins did you find a solution on this topic ? I have the same problem.

[Luke Wilkins]

Hi Farfara,

This went a bit over my head but the developer said we had to make the tables used in the scoped app accessible from the scope. This fixed it for us.

[Farfara]

@Luke Wilkins Thank you for the response but what tables and scopes.