Alteryx Designer

Find answers, ask questions, and share expertise about Alteryx Designer.
SOLVED

Conv Errors when using CReW Macros Runner

Highlighted
7 - Meteor

I have a workflow that runs clean with no conversion errors, but when I use a CReW Macros Runner to run the workflow I always get the message " Runner (3) Tool #2: The field "Field_1" was truncated in record #4".  Has anyone seen this before?   I saw some suggestions about adding a Select tool and increasing field sizes, but that hasn't had any impact.  

Highlighted
Alteryx
Alteryx

Hi @abartoszek,

Without really knowing what your data looks like, it appears your data may have a data type for field length problem. Take a look at the metadata of the first field in record four and see what it looks like.  If this doesn't resolve the issue, I suggest contacting Alteryx Customer Support at support@alteryx.com to have them take a closer look.  If can include a copy of your workflow and data in that email, that will really help them so they can help you.

Highlighted
7 - Meteor

Hi @abartoszek,

 

did you get any solution for the issue you have mentioned, If yes please let me know what is the solution.

Highlighted
7 - Meteor

Unfortunately, I didn't have time to pursue it further.  It seems to not cause me any data issues as of yet, and it's only a warning so my job doesn't fail.  Sorry I couldn't be more help. : (

Highlighted
6 - Meteoroid

I am getting the same error and have traced it to the Crew runner macro itself which is reading in an output file and trimming "Field_1". These conversion errors are stopping the runner working in the server, although it works on the desktop.

Highlighted
7 - Meteor

I did fix this a little while ago, but I kinda forgot where I repaired it.  I remember it had to do with editing the macro and changing the truncate limit in one of the tools...

Highlighted
5 - Atom

Hey,

 

The solution to this error is to set the limit on Conversion error greater than the number of errors your workflow is producing. You can find this under run-time tab in the designer window. I have attached the screenshot for your reference.

 

It worked for me.

 

Hope it helps.

 

Thanks

Parag

Highlighted
5 - Atom

Hey,

 

The solution to this error is to set the limit on Conversion error greater than the number of errors your workflow is producing. You can find this under run-time tab in the designer window. I have attached the screenshot for your reference.

 

It worked for me.

 

Hope it helps.

 

Thanks

Parag

Highlighted

Hi 

Modifying field length in Run Command solves the issue. Crew Runner -> Run Command tool--> Read Results --> Input --> change the Field Length to some higher length which  you would think appropriate for your purpose( I set to 2000 ) ..by default it was set to 254. 

 

 

Highlighted
7 - Meteor

This worked!  Thanks!  ^_^

Labels