When I use the CSV import block to update my table, I see that 300 records will be updated and 202 unchanged. Is there a way to tell exactly what Airtable thinks is being updated because as far as I can tell, nothing changed?
To test this, if I do Save Records and perform the update, and then import that same CSV again, it still says 300 records will be updated and 202 are unchanged.
I don’t believe there is. One of the issues with Blocks is that they are like little black boxes; they pretty much conceal what’s really happening under the covers. Zapier and services like it are similar in nature - they do what they do and one of the aspects that make them so compelling is you don’t need (or want) to know how the sausage is made.
My hunch is the behavior you are seeing is intended and likely related to one of these caveats in the process:
Any of these constraints could explain why the process outcome doesn’t seem right.
If you need precision updates with process rules that go beyond the standard CSV block, it might be time to build a seamless integration from wherever the CSV data is being generated. But beware - importing new records and synchronizing data are two very different ideas. At a glance, the code to do this seems pretty simple, but there are several devils in the details depending on the data, the data types, and the requirements.
I’ve been experimenting with an API process that works like a CSV import block (a proxy web app of sorts) but is built like a toolkit for power-users to dip their toes into the coding pool. It leverages Google Apps Script which is free for even free Gmail accounts. Happy to share it with you when it’s more complete.