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.
"The other example was an output tool that was giving me this error: "An unknown error occurred in II_PushRecord". This was caused by a fatal truncation error in SQL. The problem was solved by putting a select tool ahead of my output tool and forcing the field to match. I could have solved that a lot faster if Alteryx had giving me the error from SQL instead of the cryptic PushRecord one."
Wow @Joe_Mako - it's incredible that you found this!
@djoyus1 - if you want me to try to recreate this, I have my own SQL server at home, and I'm happy to help. All I'll need is the table script (create table xXX) and your flow, and we can see if I can get down to the bottom of this by running a SQL trace server-side to see what's going on and what the actual query and error are.
Let me know - this feels like something that may be worth us doing a bit of extra work to dig into the underlying cause so that we can hand it over to the folk at Atleryx to fix.
Good catch! I'm surprised that this became a problem because the variable length strings are supposed to auto-trim - were you perhaps creating a table during the write phase (and the table create process was breaking)? If you were putting it into an existing table then this is very odd because SQL should have trimmed this back to the size of the content in the string.
@SeanAdams - Confirming that it was an append in the output, not a create table. I didn't realize the variable length type was supposed to "auto-truncate"? If it's supposed to then that feature indeed failed. All I did was change the length to correspond to the field length in the (append to) table and the workflow ran as how I intended.