Computed Value Different After Using Customer Action ADD ROW to Another Table

Dear Community

We have a Invoice Main Table with 1 If-Else-Column (we also tried using Template column to get the final values) with this Values that are Guid ID set for each Login User, COmpany Acc, Student Acc etc
{
“CreateOperate”: {
“UserID”: “a0eb62ed-da29-41d8-88eb-179943cc468d”,
“UserName”: “Luke”
},
“InvoiceID”: “c61fe173-fd97-480a-89a9-e9ce236e916a”,
“PuserID”: “cb05dd1b-50d1-446b-a868-1b5ba5d12925”,
“ClassID”: “aebbf86a-c7e2-421c-8358-8b821f23a84b”,
“UserID”: “43167b97-10de-4c96-84bf-fcfc2ff6284e”,

The above are correct values. Using Relation to Original Table

We wanted to export the above values to another Glide Table - Invoice - Temp using the customer action: Add Row:

However all the IDs are different in the Invoice -Temp table


These values using Custom Action: Add Row are not correct.

Kindly advise why this is so and the difference?

Any advise will be most appreciated.

Some of what I see in your screenshots looks… odd.

For example, what is the purpose of this column :point_down: ?
Screen Shot 2022-11-26 at 3.33.16 PM
I find it really difficult to imagine a scenario where that column makes any sense whatsoever.

Also, it looks like you are inserting a JSON string as a column value, here…


Is that really what’s intended? Maybe it is, but again it seems odd.

As to why you’re seeing a mis-match in values, impossible to say why without understanding your full setup in detail.

Just out of curiosity, why are you using the API to copy data from one table to another?
Again, it seems like a really odd use case.

Hi Darren, thanks for the prompt reply!

From this screenshot, these IDs are required to be pushed to our DB via API.
This are the values

{
“CreateOperate”: {
“UserID”: “23007da9-72af-4508-99f8-fa250852bfa2”,
“UserName”: “Luke”
},
“InvoiceID”: “c61fe173-fd97-480a-89a9-e9ce236e916a”,
“PuserID”: “aeb5ad15-5763-46c2-98bc-a005e4c07310”,
“ClassID”: “f9829540-bf64-41c9-9890-e8333ce6e4e4”,
“UserID”: “4783bdcb-f40f-4db2-8ee0-1038622216de”

We thought that computed values cannot be read by API. thus we have used another column to record this via Custom Action : Set Column

but these ID values are different (See UserID = student ID)
“CreateOperate”: {
“UserID”: “dd2fb186-b44b-4616-b925-32e838582c3d”,
“UserName”: “Luke”
},
“InvoiceID”: “c61fe173-fd97-480a-89a9-e9ce236e916a”,
“PuserID”: “8238205f-dd51-49db-a41e-ea6a3b9d9148”,
“ClassID”: “ce1996d8-f2ee-4954-9c8c-545b0da904bd”,
“UserID”: “e5e05567-aec3-40fa-acd7-aa24cf024d44”,

Not sure why is this so.

User ID is the student ID:

The Final Values from Custom Action : Set Column wasn’t from this list.

Don’t know how glide changes these set of values.

All the above values are Lookup from other tables:

From the Various Table, these IDs are generated using Template - Unique Value

Could this be the reason?

We are extracting the Column values as JSON.

Just out of curiosity, why are you using the API to copy data from one table to another?
Again, it seems like a really odd use case.

We use a temp table to screen through new rows that need to be updated to our DB, instead of scanning through the whole Original table.

There isn’t much documentation on API, and thus we can only trial and error here and there.

We are using add-row-to-table as shown in the API documentation.