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.
Find answers, ask questions, and share expertise about Alteryx Designer.
It's the most wonderful time of the year - Santalytics 2020 is here! This year, Santa's workshop needs the help of the Alteryx Community to help get back on track, so head over to the Group Hub for all the info to get started!
You should not require adding a post/pre sql statement. If you went into SQL Server Management Studio>Design> and then set primary key it should be fine. Make sure that you saved the table after you set the primary key and are able to set the key (user restriction). Update Insert should work just fine then. Can you send a screenshot of the table with the key set? Best way to validate this is to check the table again under design and you should see the key already visible.
If you have a post or pre sql statement that adds the key I would think you should remove it as you won't require that after the first run; try that as well if you already have keys set.
To add on, the "Update: Insert if new" works well with Unique Primary Key on the table. If you have only a primary index, it fails with above error. But when it comes to handling million records, the work flow becomes slow.
Please let me know if you faced the issue and is there any solution for this ?
How many columns do you have in this table. when you do upsert, Alteryx expecting more than one columns, as primary key is not be updated in upsert. If you don't have nay other column beside primary key in the custom mapping then you will get this error.