I'm deactivating a custom field in my instance. What is the easiest, most efficient way to identify Flow Designer Flows/actions/subflows that may be impacted by this, i.e. trigger conditions, scripts, etc..?

[Dustin9]

I've deactivated a handful of custom fields my organization is no longer using. I know how to identify various different scripts, policies, business rules, traditional workflows, etc.. that may be impacted by this. However, I'm not sure how and where to query Flow Designers that may contain these fields within their conditions or script actions. What is the easiest, most efficient way for going about this? 

[Tudor]

Hi Dustin,

If you really don't want to put in the work you can write a script that loops through all the tables that extend the sys_metadata table and search in each field whether your fields are called.

This way you will find all the entries, but, disclaimer here:

1. you can have the same field defined on 2 different tables - meaning you might get more results that you wish
2. I don't know whether there are any tables that extend tables that extend Application File(sys_metadata)

Hope this helps!

 Tudor

[Roy Verrips]

I may be oversimplifying this, but I am able to locate all custom fields used in my Flows using a simple "Keywords are" (or "for text") search in the Flow Designer list. 

Did that not work for you, @Dustin