Hello. My current workflow inside n8n duplicates a basic row with generic fields perfectly. The problem I have is one of the fields I need duplicated is a file field.
At the bottom of the (Create Duplicate Task - create row) node, it has the following disclaimer:
“Hint: Link, files, images or digital signatures have to be added separately. These column types cannot be set with this node.”
So it gives a wonderful disclaimer, then doesn’t offer me any information on how to go about this the right way. And unfortunately, I can’t find any documentation on this.
So can anyone give me a general idea on the right way to go about duplicating a row that also includes a file field/column? I read something about the merge node in another thread, but I couldn’t really make heads or tails out of the discussion.
Actually (as far as I tested), the behaviour is not the same for links, images and digital signatures on one side, and files on the other side. You’ll need an extra node if you want to create a link, copy/upload an image or digital signature or upload a new file, but if you just want to duplicate a row including its (already uploaded) file, it’s pretty straightforward: I can’t see how your Create Duplicate Task is configured, but if you chose Auto-Map Input Data to Columns as Data to Send option, the file should be automatically copied, and if you chose Define Below for Each Column, you can just Add your file column and drag and drop the content of you original row from your input node into the column value field.
Hope this helps…
Thanks for the reply Benjamin. I’ve actually tried both auto mapping all fields as well as defining each individual column. And both create a 504 gateway error on the execution. When using the “Define Below Each Column” option, it runs fine and duplicates the row as expected as long as I don’t include the file column/field.
I’m not a programmer, so I don’t like messing with the command line stuff on the server myself which I’m guessing will be necessary in order to increase the timout parameter to solve the 504 error. But I’m not even sure this is what is causing the hiccup here. The attachement I used to test was a simple png file that’s 5 kb. So that shouldn’t cause this whole process to extend past 1 minute with such a small attachment. Especially considering the successful executions are near instant when I don’t include the file column/field.
I think what I’m going to do here is when the next update is released later this month for seatable server, I will get some help to update to the latest version and in that process, I will have them increase the timeout parameter as well as install the python functionality which wasn’t done on the initial install. Then I will reevaluate.
Thanks again for taking the time with your recommendations.
Hi again Kevin. It could be interesting to know more about you’re setup : do you use SeaTable cloud or self-hosted ? Which version ? Knowing the version of n8n and of the n8n-nodes-setable community need would maybe help (at least me ) to understand why I can’t reproduce your problem.
Again, I am not a programmer - so I dummy up with a lot of this stuff. But I was looking through the execution logs on n8n and there were 2 different messages on the errors. The first was 504 gateway time out and the other was: Execution stopped at this node n8n may have run out of memory while running this execution. More context and tips on how to avoid this in the docs.
I can’t imagine there would be any memory issues though as I’m using a 32GB server for easypanel with nothing else on it.
Hi Kevin,
Sorry I’m afraid I won’t be able to help you: I thought of a version problem but you’re actually more up-to-date than I am . At least, I unsolved your problem hopping that someone (maybe @cdb?) could help you…
Hi Christoph. I actually had some other things wrong too in my workflow. So your short tutorial here with images helped me figure it all out and everything is working as expected now.
) to understand why I can’t reproduce your problem.
