-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect Update Results #544
Comments
Thanks for all the details! I’ve recently identified an error with virtual tables where they appear to support the newer |
Yep - that gets it to work, although now I hit the API rate limit after about 100 updates. |
Interesting, can you post the details of the error you get please? It should normally be handled with automatic retries by the underlying service client. |
Sure thing - see attached! |
Very strange situation here - I've tried structuring this update a few different ways, and I'm getting the same results.
Here's my query:
If run the select in the in () clause, it returns 43 rows:
when I run the update, it says it will update 43 rows:
I hit yes and it says it updated 43 rows:
but the table still has 43 records marked STALE:
wdi_ivueworkordersimported is a virtual table held in SQL Server. wdi_ivue_wo_mstr_view is a dataverse table.
I also have several other tables following the same pattern, and my update for those tables works as expected (set wdi_importstatus = DONE when the hashstring values match).
here's the execution plan from the update in case that helps:
The text was updated successfully, but these errors were encountered: