I am doing a comparison between two data sources, one a google sheet the other a database. I’m attempting to do an upsert at the end and all was working until I added another data point that is nullable. The workflow is supposed to transfer data from an internal sheet that houses some user information, then updates our database with it. However, some data can change like first names and last names, but there are some immutable data points. There is another workflow that fires off after this one that generates a user inside of our CMS and then updates the user’s information with the ID assigned by that CMS. For some reason, when adding that data point and making it nullable, the upsert no longer attempts to search for the immutable data and just inserts a new instance of the data.
- n8n version:1.11.1
- Database: MySQL
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app): Cloud VPS
- Operating system: Alma 8