Every time after changing the order of columns in “Mapping Column Mode” → “Map Automatically”, I get this error from google sheets.
In old versions of google sheets in Map Automatically mode there was no such error, always when adding new columns, the system did not rely on a specific order of columns, but found and filled columns based on column names as keys, and filled exactly these columns, and if there were no such keys, it added them.
When exactly this order was knocked down I do not understand, but now it is absolutely difficult to work, because when customizing I often remove renamed, change the order or delete columns.
What is the error message (if any)?
Column names were updated after the node’s setup
Refresh the columns list in the ‘Column to Match On’ parameter. Updated columns: profilePicUrlHD → igtvVideoCount, igtvVideoCount → postsCount, postsCount → businessAddress, businessAddress → error, error → isRestrictedProfile, isRestrictedProfile → restrictionReason, restrictionReason → profilePicUrlHD
This is due to changes in the work of Google Sheets node if the columns often change in the document,
I recommend as a temporary solution to change the version of the node from 4.5 to 3.0.
In old versions of node google sheets in n8n automatic data entry did not depend on the order of columns. And it was a perfect solution. now anytime you change columns in a sheet, the script gives an error, It’s super not convenient and negates the stable work.
I ran into this error again today. It is very inconvenient to go to the workflow scenarioevery time after changing columns and manually rescan the columns.
Thanks for the extra info!
I’ve created an internal ticket to take a look at this and fix it. We’ll update you once it’s released.
For now the workaround continues to be refreshing the columns list in the node to have it match the new G.Sheets params.
@adamchu22 you mentioned you see this even if you don’t edit the columns’ names. Are you seeing the error from the first set-up?
Can you share what your use case? It could be something else
It makes impossible to use the workflow for multiple sheets. In my case, the sheetId is dynamic and passed as an argument into the workflow, so the same workflow is used to write rows in different sheets with different schemas.
I expected that “Map Automatically” means that it reads the columns of the sheet during runtime, but as I see now, it caches them during build time and tries to reuse whatever cached schema independently of the actual sheet referenced by sheetId.
Hope it will be fixed soon! thanks!
Yes, It has always worked this way before, any sheet with auto-transfer functionality will pass any keys and values, check my workaround with downgrade node (in any editor, like notepad) **“typeVersion” ** to 3 (from 4.5), it might be ok with you
