I've run into a Roadblock with Big Tables

Ask for Help
1

Hey guys!! Wondering if I can get some assistance.

I have a Make.com API that writes a list of data to a big table in bulk, say 50 rows at a time. Some time in the future, I have that same user export the same data again plus or minus rows of changed data, lets say this time they export 48 rows of data to a DIFFERENT New table which I call “The Working Table”, I want glide to look up the differences between the Original Data and the “The Working Table” and give the user the ability to update the old data with the new data, which we will call ‘Merge Changes’. I am running into a roadblock where I cannot have big tables display any of the boolean or computed data at all. I have a boolean setup that looks for changes in and if - else type setup, but I cannot seem to use that if-else for anything good. I’ve tried to make my working table a Glide Table, and a Big Table, But they don’t talk to each other properly. Reason I need a big table is because the dataset will be large.

maybe there is a better way to do this all together? please help :D, the use case is parts and part numbers, prices etc… that get updated in an external application which pushes new changes to the API in Make, and I need to reconcile these changes to the user inside the app.

I need it to: Make changes if there are new changes on the new data table, delete lines from the parts order if they are deleted on the new data table, and add new parts if they are added to the new data table. It is not optional to delete all lines, and write new lines as there is some data that must stay inside glide, that doesn’t come from the outside source (77 columns of data, 50 or so come from outside source, the rest are edited within glide)

Thanks in advance, I know you guys have crossed this bridge before :smiley:

I can’t even sort a table by my boolean of “Changes Required:TRUE” Frustrating at this point

2

So can your case be summed up like this?

  • You need assistance with merging data between two tables in Glide using Make.com API.
  • Original data is in a Big Table.
  • New data is exported from external source and imported to a different table called “The Working Table.”
  • Goal is to update the original data with changes from the new data.

I would do it like this:

  • Main table stays a Glide Big Table.
  • Only have columns that comes from outside sources in that table.
  • Have a new table, to also have those records, but with columns that can be edited in Glide.
  • Use relations & lookups to bring those fields to the big table, or vice versa.

Every time you update info from external source, do a stash and fully update the table (i.e clearing the old rows and updating the whole set of rows from external in).

1 Like
3

Thank you ThinhDinh, this is the way I had it configured yesterday. I did use that with a few alterations and additions!! But yes that is the overall solution!!

4

The whole Idea is dead in the water anyway, the updates consumption is through the roof.

I thought batch updates thru an API would send only one update, but each update within the mutation json is sending an update.

Thats too bad

5

You should use the stashing API for Big Tables. Are you familiar with that?

6

Never heard of this sir, I am going to look it up !

7

Let me know if you need any help.

8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.