Flow Designer - Subflow not able to reference information from Input record after Xanadu upgrade

[ryanpewing]

There seems to be an issue with a subflow after the Xanadu upgrade. We use a subflow to Create a Catalog Task consistently, adding variables, Due Date, and other attributes. We input an Assignment Group to that subflow for the task to be assigned to that group. After the Xanadu upgrade, the reference to the Assignment Group looks different.  Also, when I try to reference attributes of the Assignment Group in the subflow (name or sysid), it comes back empty

Flows created before upgrade - SysID is used from the Flow Variable to create the task

After upgrade - It attempts to use a string version of the Name + SysID

[Ankur Bawiskar]

@ryanpewing 

the assignment group is set with value from flow variable

How is that flow variable assigned value?

share the complete subflow screenshots and also the flow variable step where you are setting the value to it.

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

[TrentE · Accepted solution]

Hey Ryan,

Seeing the exact same issue. I do believe it's worthy of a HI ticket. However, as a work-around I've found two options:

1. Either change your Subflow Input to a "string" value and pass in just the SysID of the Assignment Group you're looking to use. (Make sure the assignment at the task level is using SysID as well - the system will recognize and fill in the missing details)
2. Perform a lookup of the desired Assignment Group before hand and pass the record result into your "Reference" subflow input. This somehow passes the "entire" record, rather than the stringified version.

If you do open a HI ticket - share the results if you can. Hope this help!

Regards,

Trent

[ryanpewing]

Ultimately, we did initiate a HI case for this. And there feedback was about the same as this. There is a Problem that ServiceNow has opened to identify a fix for the issue, PRB1861596. But for the time being, we went with the approach to pass the sysid into the subflow as a string. 

[Nicolai S]

Experiencing the exact same thing when calling subflows containing Reference inputs created before Xanadu.

My workaround is performing a lookup of the record and then passing that to the subflow instead of just selecting the record.