This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
I could be wrong, but it looks to me like this macro isn't doing anything at all... You need a macro input to actually run your data through the detour tool.
Even then I'm not sure this is going to do what you want. Batch macros run the entire data stream through a certain number of times based on the control parameter. So, I think you will want that to be a single value. Again, I could be wrong.
Either way I think the error is being triggered because you have no data flowing through the macro.
Interesting. So the reason this error is actually being triggered is because the detour tool does not continue processing on the inactive side. Meaning it doesn't even pass 0 records. It is almost as if the unused macro output didn't have a connection. I would recommend using a 'Detour End' tool to bring the two streams back together and using a single Macro Output.
I build a batched macro and then put that macro in my main workflow, and it worked the first few times and now I get an error saying "Record #1: Tool #5 Parse Error at Char(53): Unknown Variable "#1" ... output connection "Report_Date Macro" was not valid" .... how can the workflow work most times and not now? Anyone get this type of error before?
It accepts a date field as input. Note that it does not use the Input tool but the Text Input tool to create a placeholder date that will be substituted. I also set the control parameter name to describe what to connect it to via the questions tab you will get when connecting it to your workflow.
Sometimes the errors are non-fatal in that they describe a data type error. That is the control parameter may be expecting a date vs. a string for example.