Parse Error on Formula

[DrewCroft]

I have a macro that uses a Formula tool.  There are two fields:

  

The SubcategoryRaw field is coming from a Select tool that has it configured as a V_String 255.

 When I test this macro workflow, the workflow outputs perfectly with no errors.

When I attempt to use the macro in a workflow, I get errors pointing at the Formula tool expressions…

 What gives?

[binuacs]

@DrewCroft @Can you check the data type of subcategory field in the append tool? Also can you try running workflow after turnoff the  AMP Engine?

[DrewCroft]

Thanks for the response, @binuacs!  

Turning off the AMP Engine didn't change anything at runtime, unfortunately.  The settings for that Append tool are below:

[binuacs]

@DrewCroft Without seeing the macro trouble shooting is difficult, can you try to run with different input files to see there is any change. 

[DrewCroft]

I understand it is difficult to debug without being able to get your hands dirty with it.  Unfortunately, the data I'm working with is proprietary and I cannot post it.  

I do know it happens on EVERY file (there are 50+).  The macro portion works without trouble if it is standalone but if you toss that into a batch workflow, the error on the Formula pops up.  The syntax for both formula seem good, I'm not sure what's going on.  ;__;

[binuacs]

@DrewCroft what the action yool settings inside the macro, can you screen shot the settings here

[DrewCroft · Accepted solution]

@binuacs : Thanks so much for your time, I figured out the problem. 
The data going in was definitely set as V_STRING in a Select tool, but for whatever reason the Formula tool didn't see it like that.  I resolved the problem by squeezing a ToString() around the field reference in the formula... so it went from:

Left([SubcategoryRaw],2)="  " 
to 
Left(ToString([SubcategoryRaw]),2)="  " 

This solved it!

I blame Excel for issues with data interpretation.  I'll just make certain to use ToString or ToWhatever when these errors pop up.