Incompatibility Issue with Flow Design

[terrieb]

We just upgraded our Dev instance to Xanadu and I updated a flow design in that instance and added it to an update set to move to our Test instance, which is still on Washington DC release.

Got this error message in the Update Set Log:

I noticed that if I update or create a new Flow in Xanadu release instance, the references to either the Request or Requested Item to update that record, end up displaying like this in the Flow:

Whereas in Test and Prod instances, it displays like this:

So obviously this was changed in Xanadu, but I see nothing about it in the Release Notes and it is making us recreate revisions or new Flows in our Test instance to move up to Production.

Is there a BR, Script or something else that is causing this that I can deactivate for now until all of our instances are on the Xanadu release?

Thank you

[Ankur Bawiskar]

@terrieb 

Seems to be an issue with Xanadu version.

this link talks about the same issue and has some workaround/response from ServiceNow but you need to have HI credentials to view the KB

Table 'sys_hub_trigger_instance_v2' does not exist 

If my response helped please mark it correct and close the thread so that it benefits future readers.

[terrieb]

So in other words, we can't build or revise Flows in our Dev Instance in Xanadu to move up to any other instance that is still on Washington DC?

Guess we will just have to do everything in Test to move to Prod and then after we upgrade Test, we will have to do any changes "live" in Production until it goes to Xanadu.  Great way to break a developer process that we have been using for years and years...

Also absolutely NO reference in the Release notes about this major change.  That would have been nice to know about in advance as well.

Thank you

[maheshladdha]

Hello @terrieb 

Have you got any other solutions? We stuck on the same issue now.