RITM variable value not updating

[Bidduam]

I have created a custom flow action to update a variable value as shown here by @Maik Skoddow :

Set Value of a Catalog Variable at Flow Designer - ServiceNow Community

I have used it in the past successfully, however I've only used it as a true/false or yes/no

This time I am trying to set a date value and it just isn't working, even though the flow execution says that is should have.

I have also tried over writing an existing date value with the new date value, along with trying to write it into a completely new field both as a date field and a text field. I've also done a convert date to string as part of the flow.

The field in the RITM just never actually updates.

These are the fields I'm trying to update: (I don't care which one I need to update, one or the other is fine, just trying multiple ways)

u_start_date (date field)

u_csd (text field)

The flow action:

I am getting the RITM to update in a previous flow action.

The execution log shows that it should be working:

Ideas?

[DaveMerrett]

@Ankur Bawiskar That was absolutely going to be my next suggestion.

[Bidduam]

@Ankur Bawiskar So how do you do the lookup variable ownership record?

Presumably that's important to actually be able to update the value?

[Ankur Bawiskar]

@Bidduam 

you can use the parent field on that table, it holds RITM sysId

So you can use that

In the screenshot I am using Lookup on Variable Ownership with Parent=RITM SysId AND the Question you want to update

Then I am updating the Dependent question record with the value you want to update.

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

[Bidduam · Accepted solution]

@DaveMerrett & @Ankur Bawiskar 

So my final solution was to delete the flow I'd created and create it again. I used the exact same action to update the variable value that I'd used originally, but for some reason this time it is working 100%. Maybe I've done something slightly differently (although it looks exactly the same to me) or there was some sort of corruption in the previous flow?

Anyway thank you both for trying to help.

[DaveMerrett]

@Bidduam Thanks for the update - Sounds like something in the backend wasn't meshing up correctly. But by redoing it, you recreated all the associations and relationships of that record / flow. 

That was what was causing me to scratch my head, as what you did should of just 'worked' but glad you've found your answer 🙂