Both approaches should work. If they don’t then I’d consider that a bug.
2 Likes
I realise this is an old thread but just wondering if there is a performance difference between these two approaches?
In my glide big tables, if I have a relation between two tables, parent and child, with a Unique Identifier Special Value in a text column of both of them or with a rowID from the parent table to relate to the child table?
There shouldn’t be a difference in performance. Usually I just use rowIDs, but I haven’t had a case like what V88 suggested here recently.
Nowadays, you do have the action to write a rowID somewhere after an Add Row action. You can write it to a User Profiles column, and then reference that column in the “child” Add Row.
great thanks! yeah that write row ID to is great, the problem is that I’m using the glide API to bulk add rows, so many different parent rows with many different child rows, might see if I can use the API response to query the right rows etc
You would have to loop on the parent level to be able to do the same thing.
E.g: Loop #1 - Add parent: the API returns a rowID in the response - Use that for the loop on child rows.
Then loop #2 etc.
yep sounds like a plan! thank you
1 Like