Change REQ issue with the 'Submit Catalog Item Request' Flow Action

[chanp]

I need to submit a procurement catalog item within an existing Flow of a primary catalog item and relate it to the same Request as the primary catalog item's. The flow action does not have a field for Request and as per my research, the essence of this action is to submit another Request. I can manipulate the RITM of the procurement catalog item to change its parent REQ just fine but I'm having trouble in changing the REQ of the sourcing task. I did a lookup to grab the sourcing sctask by using the REQ of the newly submitted procurement request then used the Update Record action to change the REQ of the sourcing sctask. Afterwards, assuming the new REQ is now an empty shell, I can go ahead and delete it. The weird behavior that's happening is that the sourcing sctask does not appear in the Catalog Tasks tab of the main REQ. In the list view for the sctask table, the sourcing sctask has still got the new REQ as its parent but when you open the sourcing sctask, the main REQ actually appears on its Request field kinda like a cluster issue. Is there another way to accomplish it?

[Ankur Bawiskar]

@chanp 

you should use Lookup Records and the use For Each on that iteration and then update the task

From your image it doesn't look like you are iterating and updating.

please do that and share feedback

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

[chanp]

Found the missing piece here. The Catalog task record has both fields Parent and Request which point to same REQ number. Make sure to update both fields (specially the Parent field) on the Update Record action in order fully move it to a different Request. The filter in the Catalog Tasks tab is actually using the Parent field not the Request field.

[Ankur Bawiskar]

@chanp 

Glad to help.

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