I don't see my custom Table and not extended to Task in the Flow Designer

Elias Beylouny
Tera Guru

Hi Experts

I have a custom table created NOT extended from TASK and is in a custom scoped Application.

I am trying to use this table in the Flow Designer but I am not able to see it. 

Is it possible to get this table to be seen in the Flow Trigger Dropdown without being extended to Task?

Thanks

Elias

1 ACCEPTED SOLUTION

Hi All

 

I  got a feedback from ServiceNow and this is the solution : It is now working.

 

Most Probable Cause:
This has been recorded as PRB1573653 for which a Known Error article has been created KB1117260.


Solution Proposed:

To fix this check that the table includes the Domain and Domain Path columns. If they are not there, add them.
Then do the following to clear the session storage cache.

The session storage cache must be cleared. The API results for fetching the tables has been cached for a the original domain and because it is caches it is not being re-fetched for changed domain.

To do so there is two ways:
First one is to close the Flow Designer tab and reopen it after the Domain has been changed
Second one is to open the browser console, type sessionStorage.clear() and hit enter. Then refresh the browser window and the table should appear in the list.

View solution in original post

13 REPLIES 13

I am not 100% sure but it looks like.

I just wanted to know if this behavior is normal or not on all instances.

 

Elias

also weird just checked in the same Flow , in the Action = If and Update Record I can see this table, The only place I cannot see it is in the Trigger.

 

find_real_file.png

Did you check in any other instance which also had patch update?

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

I checked my Production and Test instance and there also having the same issue.

I didn't checked a demo instance yet.

I assume maybe they added for the Trigger Field the filter not to show not extended table.

or there is an ACL Read restriction now for that.

 

Hi,

Did you try creating new custom table in your scope and verify?

Regards
Ankur

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader