@Jeff_Hager well - these can be used when you do an action. This won’t work for me
I have four “objects” on one line. I need to reference between the objects so when I do put the different “objects” in their respectively tables then the references are in place. That’s why I need the extra guid’s
@Darren_Murphy I have a JSON object with a varying number of lines
On each row (row 1…50) in a table “data-import” I pull the data from the JSON object by use of Query JSON columns. Some data belongs to “object” house, som data belongs to “object” garden, some to the “object” flowers. I will put the data afterwards to three tables by use of call API - house, garden, flowers. But I need to refer the garden to the house, and need to refer the flower to the garden.
On each row I only have access the the rowid as GUID which is to be used as the key between the related tables.
I would like to get a globally unique key for each row (independent of whether it is found in house, garden, flowers.
So how do I create three guid’s on each row in “data-import” table
The setup I have today gives me a key (rowid) which is unique within each table
The JSON object doesn’t have single unique key for each line-object
Okay, so it’s more complicated than you first described.
If I’m understanding correctly, you essentially have a hierarchy where flowers belong to a garden, and a garden belongs to a house, yes?
If that’s correct, I think I would take a slightly different approach. Rather than trying to pre-generate the UUIDs I would just use the RowIDs that the Glide API returns. So the flow would be something like this:
Add a House record, and capture the RowID that the API returns
Add a Garden record, and set the HouseID to the value captured at the previous step. Capture the returned Garden RowID record.
Add a Flower record, and set the GardenID to the previously captured Garden RowID value.