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

Go to solution
fn83
Tera Contributor

‎01-31-2025 01:36 PM

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

ryanpewing_4-1738359244236.png

 

 

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

ryanpewing_3-1738359211883.png

 

 

0 Helpfuls
  • 2,885 Views
1 ACCEPTED SOLUTION

Go to solution
TrentE
Tera Expert

‎02-01-2025 07:21 AM

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

View solution in original post

5 REPLIES 5

Go to solution
jeffreyluto
Tera Contributor

a week ago

For clarification what exact version of Xanadu

0 Helpfuls