BLUF: I am trying to use a scenario to copy the majority of fields in a reimbursement request database into a separate reimbursement approval database. The field that is causing issues is the “files” type, where I’m collecting receipts pdf/jpg files. It’s foolishly not a direct map (despite coming from and going to the same kind of field in the same application).
I read this previous post which was helpful. However, it isn’t clear to me how to get the aggregator to work correctly in my use of it.
I am using a scenario to “watch” a database and then “create” a new database entry in a second database based on a submitted trigger in the first. I am successfully mapping all the typical fields from the first to the second (numbers, text, etc.), but I also have a field for files (scans of receipts). I want to be able to capture those from the original entry and add them to the new entry.
I’ve tried numerous tweaks (using “list content” - aggregator, iterator-aggregator, json . . .) and almost always end up with an error in the final update due to some field being wrong (including FBls which I’m not familiar with). Of note, when I select the target structure for the aggregator, it only asks for url and name, but one of the errors I tend to get is a conflict resulting from the url being internal to notion but the “type” was somehow set to external rather than file (but it didn’t give me an option to map the “type” in the aggregator).
In one set of tweaks, I was able to get the update to process, but rather than putting both files in the new entry, it put a single file, named “Integromat,” that linked to the original database entry.