# API Calls as a solution to the Filter/Search problem of Big Tables? - Price Issue

**URL:** https://community.glideapps.com/t/api-calls-as-a-solution-to-the-filter-search-problem-of-big-tables-price-issue/66895
**Category:** Ask for Help
**Created:** [October 11, 2023, 7:18am UTC](https://community.glideapps.com/t/api-calls-as-a-solution-to-the-filter-search-problem-of-big-tables-price-issue/66895 "2023-10-11T07:18:36Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)
#### Post date: [October 12, 2023, 1:50pm UTC](https://community.glideapps.com/t/api-calls-as-a-solution-to-the-filter-search-problem-of-big-tables-price-issue/66895/5 "2023-10-12T13:50:16Z")

</div>

> [@Flowcode](#):
>
> to construct a CURL Api Call for each row of the Supplier big table which I could use in an Api Call action every time I edited the name of the Supplier in the frontend, to update the ‘Name Text Log’ column in the Product Table

Yes, that’s what I understood.

> [@Flowcode](#):
>
> through creating a Joined list of all the ‘JSON Update Element’ values of the related products (which I can retrieve with the Query Column in the Suppliers Table as you can see). I could then add a Template column

That wont work - as I guess you’ve discovered - because you can’t take a joined list of a computed column from a Big Table.

However, there is a workaround - and this is something that I have used, so I know it will work.

- Start by creating a Query, matching the SupplierID of the one you want to update.
- Take a Joined List of RowID’s through the Query (this will work, because it’s a non-computed column)
- Feed the Joined List into a JavaScript column that processes the list of RowIDs, and outputs a JSON collection of API mutations, each of which updates your Text column with the new name
- Use the JavaScript column in a Call API action

As I said, this works perfectly well. I’ve actually been using the technique to good effect just in the past few days. The only thing you need to watch out for is the upper limit (500) on mutations in a single API call. If you need to update more than 500 rows in one go, then you’ll need to batch them up.

oh, I should add - even using this technique, you’ll still be using an update for every mutation - so that part of it won’t change.

---

_[View the full topic](https://community.glideapps.com/t/api-calls-as-a-solution-to-the-filter-search-problem-of-big-tables-price-issue/66895)._