I am building an automation to move records from a “Sandbox” table to an “Approved” table. Both tables have identical structures and the same option values, but because they are separate tables, the internal IDs for these options differ.
I am running into the following error when attempting the transfer: “Value error for field ‘Size’: The provided value should be a valid integer or string.”
I suspect I am misconfiguring how the option values are being mapped. Additionally, I need to know the best practice for mapping Photo fields and Linked Record fields, as these contain multiple objects.
How should I handle the ID mismatch for the option fields, and what is the standard approach for mapping arrays of photos and linked records during this migration?
The first thing to consider is if you need to have separate tables for Sandbox and Approved. Is it possible to work with 2 separate views instead where the views get filtered on a status?
If you need separate tables, and the tables are part of the same database, the Link to table field should work fine since the linked table is part of the same database. I did a test and referring to item [0] of the newly created rows instead of [All] works
Ah, views! That would make things so much simpler. I’ll have to update my application builder repeater datasource, but that’s easier than messing around with two tables.
