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.
Inspire EMEA 2022 On-Demand is live! Watch now, and be sure to save the date for Inspire 2023 in Las Vegas next May.
We'll be completing standard maintenance for our Single Sign-On system on November 30th 6pm Pacific Time for approximately one hour. During this time My Alteryx and sign-in functionality to all My Alteryx programs (Licensing Portal, Community, Beta Program, Case Portal, and others) may be inaccessible. Thank you for your patience.
It would be nice if you could see messages generated by SQL server in through the Alteryx tools that are communicating with the server.
2 examples to illustrate: I was reading in a table, Alteryx gave me no errors, just a message that a certain number of records was read in (about 5M). Since I don't know the exact number of records in the table, just that there are approximately 5M, I thought everything was ok until somebody else pointed out that revenue past a certain date was missing. Turns out that reading in the data was interrupted by an error sql was throwing on a calculated field. Fixed the calculated field and was able to read in all records. It would have been nice if Alteryx had mentioned the error instead of reading in a partial table....
The other example was an output tool that was giving me this error: "An unknown error occured 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.
I understand that this might be challenging, not sure how the SQL drivers behave in regards to reporting error messages. One workaround for the first error would be to count all rows in a table before reading it in, then reading it in and giving a message similar to the one you get from a Calgary tool (5,968 records out of 4,684,784 where read in). Maybe as an option because it might slow things down a bit?
I'm receiving the same error. I'm using an output tool to update 85k records onto a SQL database. Originally I got a descriptive error, because the table didn't have its ID column tagged as a primary key. I fixed the table and now I'm getting "An unknown error occured in II_PushRecord". Any help on this?