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'm not sure on the hiding messages part, but I am curious to the syntax of submitting 1000+ rows for a WHERE clause. In my experience, it's better to combine the conditions and execute a large. single query rather than waiting on the time it takes to submit and returns 1000+ queries.
For example: if you're updating a clause like "Where ID=1", "Where ID=2", and so on, combine the records with a Summarize tool and modify the query to use "Where ID in ([Concat_field])" in a single query.
Hi thanks for the input, unfortunately I get a DataWrapOCI: Unable to prepare the query error when I try concatenating the field. I am thinking it is due to the amount of values I would be putting into the WHERE IN clause if I try it that way.
Oh of course, I forgot there's typically a 1000 argument limit. Here's a method I used to group the records into 100-record groups. It's typically much faster to submit 10 100-record queries than waiting on each one. Also, the quantity of records grouped is easily variable.
Check out the attached workflow that shows how to use the RecordID and the CEIL function to create these groups of WHERE clause replacement values.