Getting API output into table.

But returning it should store it in that field

Any luck? Have to run to church will be back in couple hours

@heady_impala sorry for the delay.

Here’s where I’m at. It can see the output when I hover over it, I need that to be outputted as a string.

@yang any ideas?

I think I know the issue but I don’t know the workaround

hmm are you embedding this code snippet as “custom value” for a column? Unfortunately you can’t use an async value there because React won’t be able to render that… :thinking_face:

one possibility is to have another data query that fetches all the councils used in the zip codes in the first data query, but also hard to set up if your API doesn’t support fetching for multiple zip codes at a time :thinking_face:

@chungwu

The API does support bulk lookup!

I’m going to have a list of potentially 10s of thousands of postcodes here so I don’t necessarily want to query them all at once, but I’m assuming I can query based on paginated postcodes

ah then you can just query for the postcodes that are fetched in the data query that’s currently in the table (not sure how that’s setup)… like…

{ "postcodes": $queries.tableData.data.map(row => row.zip) }

@chungwu to the rescue!

My question now is: is it okay to have 10s of thousands of postcodes in my API request body? or should I paginate and only query based on those

image.png

hmm does your table’s data actually reference 10s of thousands of postcodes?

It will do, yes!

I’ll be uploading thousands of my client’s clients

ah, then you may want to paginate the data for your table too?

Indeed

Unless I hate the end user :smile:

yeah so I think once we paginate the fetched table data, then the zipcode query isn’t an issue (since it’s just using zip codes from the table data)

Ahh ok that makes sense!

So my table data is automatically → whatever is on the current page

One other issue @chungwu

Any idea why referencing this data only works inside Plasmic studio? localhost and production both give me cors issues

My table is inside the REST fetcher component. As far as I could see I can’t POST using integrations but happy to be corrected

image.png