options are not displaying upon pressing "fd_data"

Ashwini101
Tera Contributor
Available options are not displaying upon pressing "." after fd_data

 

In my flow I am using Get Catalog Variables step to fetch variable values from Catalog item.

I am using an action also in the flow and need to pass the value fetched from catalog item to action input. I am using inline script as required for this case. 

When I am trying to use "fd_data" I am not able to dotwalk. It is not prompting anything. Any Soultion?

 

For example - I have a value TSGD@12345 and I am splitting as I need values after TSGD@ as input. For this only I am using inline script and need to use "fd_data" to dotwalk.

 

 

 

#ITOM #ITSM #scripting

13 REPLIES 13

Jesper Slot
Tera Guru

I have the same issue. Utah Patch 7.

Any known workaround? 

Abhishek M
Kilo Guru

I too facing same issue on vancouver patch 2 hotfix 1, even its not working in PDI

Jesper Slot
Tera Guru

I did some digging in old flows to find the correct syntax, so I could move on. I'll just share here, maybe it can help some:

If trigger is service catalog and you want to fetch a value from that created item, then you can drill through with following:

 

fd_data.trigger.request_item.<field on table>

 

 

or for a variable set on that item:

 

fd_data.trigger.request_item.variables.<variable name>

 

 

If trigger is, for example, creation of a record, you can do:

 

fd_data.trigger.current.<field on table>

 

 

If you want to get content from a flow variable:

 

fd_data.flow_var.<variable name>

 

 

Update .. I had one more today:
I had a "step 2" with a "For Each" logic. I needed to update the records in the foreach loop with an "Update Record" action but had to script it.. following path worked: 

fd_data._2__for_each.item.<field on table>

So " _2__  " for the step and I would assume that this could be replaced with any step number followed by the for_each.item... 

Community Alums
Not applicable

Hi All,

Per HI Support, this issue is resolved in Vancouver Patch 3.

We tested this and confirmed our functionality is restored.