Dynamic Replace Macro Help

smoskowitz

Good Day All -- 

I am working on a project where I am trying to Dynamically replace header names for various templates provided to me. I thought that the Dynamic Replace tool was the answer, but what I learned is that once it looks at a column, it will not look at that column again.

I then found this article and thought, not all hope is lost:

https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Dynamic-Replace-Tool-unmatched-fields-unchanged-instead-of-null/td-p/429491 created by @iCFO.

It appears to be the answer I am looking for. However, I cannot seem to get it to work. My main workflow is slightly different and builds out all formulas based on a word I want to search and replace with.

At this point, I have spent about 8 hours trying t figure out what I am doing wrong within the iterative macro but cannot seem to do so. If someone would be so kind to take look and see if you have any thoughts, I would be most appreciative.

Thanks,

Seth

DynRename.yxzp

MarqueeCrew

@smoskowitz ,

Seth,

Thanks for ZOOMing with me and showing me your challenge. Essentially there are 3 data sources that create similar content with varying data formats. Using the naked eye and human brain we identified a simple if-then way to find the format uniquely. 

1. Input data (first row is data

2. select records 1-11

3.Create template ID based on v the cases of values, else null

4. Summarize max template ID

 now we know which column names are appropriate to each field. 

We created a document with template I'd, f#, new field name.  We can use that data with all templates loaded by joining the contents to #4 above.   Now we only have valid replacement data. 

we use a dynamic replace to assign the field names.  With warnings off, we leave extra data in the form of F#.  Using a dynamic select we eliminate fields with that pattern of name.  

now we eliminate noise records.  We identified records with a field that has 6 digits as valid data and filtered the data on that pattern match.  

finally we added a message to stop the process if #4 template ID is nulll. 

there is more work to integrate and QC the process ahead. If column ordering or columns may be added or omitted, you need more defensive configuration.  For now, error those cases. 

cheers,

 mark