Adapt Workflow to Workaround Presences or Absence of a Field to Parse

[hellyars]

Hi,

I am trying to build a batch macro for a series of XML files.  Reference diagram below.  Path A is always present.  Path B may or may not be present -- specifically the field to parse in B's second parse tool.  I found a Community solution that uses a Detour tool to account for and workaround a null value.  Here is the link.  CS Macro Dev: Conditional Processing with Detours   But, I tried modifying the Expression in the Condition Tool to ISNULL ([FieldToParse]), but it says unknown variable. In fact, it does not work with any field. 

So, how can I make my workflow adapt for the presence or absence of a field to parse without erroring out?

I am not wedded to this particular solution.  It's just something I found that I am trying use.  No doubt there is a better alternative. 

[randreag · Accepted solution]

hi @hellyars 

If I undestand you well you can use the tool Ensure Fields from the Crew macros. With this tool you can ensure the field si there even if doesnt come from the data

This Macros you can download it from Download Crew Macros 

I hope it helps

[hellyars]

@randreag  Yes.  That was I independently figured out.  That tool is becoming a go to tool.