Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

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

Cheski Frank
Tera Contributor

@Ashwini101 I am experiencing the same issue and raised a support ticket for this. Perhaps a bug?

Cheski Frank
Tera Contributor

@Ashwini101 So this is a known issue: PRB1696950: Flow Designer Script Editor auto completion/suggestions no longer working in flow design scripting Flow Designer Script Editor ( fd_data ,Dot walking )

Should be fixed with Utah Patch 8 according to support.

Not applicable

Hi @Cheski Frank ,

Can you share the details of that PRB? When I click your link I get a 'record not found'.
We're currently on Vancouver Patch 2 and it's still an issue. Did you mean to say fixed in Vancouver Patch 3!?🤔

@Community Alums CC: @Ashwini101 This is the content of the PRB:

 

Priority: High

Flow Designer Script Editor auto completion/suggestions no longer working in flow design scripting Flow Designer Script Editor ( fd_data ,Dot walking )

CS6856852. UTAH Upgrade Patch 4 to 6 broke it
UTAH 4 works

justin.rubin
I confirmed the issue on customer instance. Still trying to understand how to reproduce it. I also verified it is the same issue as CS6872591.
The issue is related to a library upgrade we made to support text-to-code. The script editor component is initializing a ts.worker.js which is conflicting with the behavior of the component.

Please open a PRB and assign to Dev-Flow Designer UI team.

 

Does that help?