globally change field cross-references

sarmstrong

Hi,
I would like to be able to repurpose workflows that share common functions across different projects. It would save a lot of time if I could globally edit the name of a field in a workflow to update all instances of that field name in the entire workflow.

So for example, if I have a bunch of formulas and that refer to a field called "Publisher" and I want to use this same workflow to perform the same actions on a new data stream where the field is called "Vendor", how can I do this without either editing my data source or hunting through the workflow to replace each instance of a "Publisher" field?

On a related note, it would also be very helpful to have a search query function to look for terms within workflows. Sometimes I can't quite remember where I put a particular operation, and being able to search for it would save a lot of time.

Thanks!

kane_glendenning

Hi Stefan,

I agree that this would be a good addition to the software. There is a similar idea on the Ideas Forum (Inherited field renaming) and so I encourage you to vote for that. 

At the moment though, you do have a couple of work-arounds. 

1. Annotations: Put the field names in the annotation on each tool, thisrences are easier to find and change.
2. Make the Data work with the Module: (rather than the module work with the data) Change the field names on your data as it comes into the module and then again on the way out. Dynamic Rename is your friend.
3. Macro/App: Make your workflow into an App or Macro and use a Global tool to 'update' all the instances of the relevant field. This of course involves setting up the workflow in a specific manner so that it can be changed easily via your action tools but you can even set it up so that you can decide which fields from your input 'map' to each field in your output.
4. Edit the Raw XML: This is a more advanced option and only recommended if you don't feel that any of the above suit. If you feel confident enough, you can edit the Raw XML of the Module. This will require Backups and delicacy. Depending on how involved your module is as to how much time this will take. I definitely advise naming your fields uniquely if you use this method and take care.

That being said, definitely check out the Ideas Forum and vote for the suggestion I mentioned in the first paragraph. If I had the time I would look at possibly making a module that edits the XML of another module and changes field names but that kind of time may be pipe dreams....

Kane