Hi,
I just updated my n8n-nodes-seatable from 1.5.2 (pretty old I must admit !) to 1.6.3 and I can’t activate any of my workflows, because the seatable action nodes type changed from n8n-nodes-seatable.seatable to n8n-nodes-seatable.seaTable (the type of the trigger nodes remains n8n-nodes-seatable.seaTableTrigger so they don’t cause any problem)…
The correction is pretty straight-forward : copying all the workflow in a text editor, replacing n8n-nodes-seatable.seatable by n8n-nodes-seatable.seaTable and pasting the result back in n8n, but it will take me some time and I’m a bit surprised: I didn’t find anything about that on the forum, did I miss the info ? Am I the only one having this problem ? And the vexing question for the SeaTable team: are we talking about backwards compatibility ?
Don’t get me wrong, I still love you all and I’m still a big fan of SeaTable
The n8n developers asked me to do this change to fullfill their naming policies. Still I thought this should be no problem and automatically updated automatically as soon as you update the community node.
Regarding your complaints: we do our best to develop and improve SeaTable and the complete eco-system without friction for any user. Sometimes this works not as expected and we are sorry about that.
Hi Christoph,
Thanks for your answer. It’s weird that I had this problem whereas I was already on 1.5.2 before updating (it was my first update, I got 1.5.2 when I activated n8n for the first time), but the name was still the old one (from before 1.5.1)
About my “comment” (it wasn’t really a complaint ), as I said, I know you do your best, and as I said, you do it pretty well in my humble opinion!
However, it is sometimes complicated to keep everything working after updates (you’ve seen I also encountered problems with the python API after this update), that’s why I opened this thread to see how it could be possible to think together of a solution to avoid side effects. As you answered me, this is a particular and pretty rare situation as it is a major version update.
Anyway, for this particular problem, it was disturbing, but no big deal to fix.
ouch … I’ve got about 20 Workflows that I have to fix, thanks @bennhatton for the hint about replacing the name in the exported json.
Here’s how I did it on a mac,
), as I said, I know you do your best, and as I said, you do it pretty well in my humble opinion!