Need help : getting Error when I trying to pass the API mutation template column as joined list in BigTable

Hi Guys,

I have template column in my Big query table which has all values of the show API for API mutation.

I am passing it into a joined list separated by comma column in the same Big query.

it is giving me this error When I am saving it.

Is it something that is not allowed?

Thank you in advance for help.

Regards,
Dilip

Hi Guys,

What is the workaround if I cannot pass template column in glide big table ?

Regards,
Dilip

As a workaround will I need to create two tables one normal glide table where it will work,

and One more glide big table? or is there any other workaround?

Regards,
Dilip

Hi @Darren_Murphy Good day to you.

You had suggested to use Glide Big tables for filtered data to be available in Api response.

but as I read it there are restrictions on only 100 rows for computed columns and Getting error for Template column to be passed into a joined List.

Are these restrictions on platform or is there something I am doing wrong?

Regards,
Dilip

This is in the data editor, it has nothing to do with the API.
Computed columns are not available at all via the API.

Thank you for your reply @Darren_Murphy .

What is the error I am getting when I am trying to pass the template column value to Joined list column to separate by comma?

it says Computed Column is not supported on this data source?

but if I do it in normal glide table there is no issue.

Thank you in advance for helping out.

Regards,
Dilip

Hi,

After multiple attempts of removing/adding.

now I am getting this warning.

Screenshot 2024-09-03 at 1.17.05 PM

Is there something I am doing wrong?

Regards,
Dilip

That’s correct. Lookups and Joined List of computed columns in Big Tables are limited to 100 rows.

Hi @Darren_Murphy ,

Thank you for replying. SO if my table will have more than 100 rows then this wont work?

Could you tell me what can I do as a workaround? I am pretty sure I will have more than 100 rows coming in very very soon.

Regards,
Dilip

It’s only an issue if you expect more than 100 matching rows.
If you want a Joined List of more than 100 rows, then you need to work with non-computed columns.

Hi @Darren_Murphy ,

Matching rows is not same as total rows?

I would need that as my template column is the API mutation column which has my values

I will be passing this to Joined list column.

Can you please help me as to how I can use non computed column to get this same thing done?

EX:

Regards,
Dilip

Not if the Lookup/Joined List is done through a Relation or Query.

The only thing I can think of is to add the JSON Object into a non-computed Text column when each row is added to your Big Table. Then you wouldn’t be subject to the 100 row limitation.

Hi @Darren_Murphy ,

thank you for replying.

No my Joined list is taking template column as input. Where I am replacing the mutation values with API value. They are not Relation or Query

Then I wont face any issues right ? Do I need to use the solution you gave?

I created JSON Object with required Fields Then passed it via template column. But it still generates every row values. I cant use joined list right , how can I get all names list separated by “,”?

Regards,
Dilip

@Darren_Murphy

Do you mean the workaround is something similar to this?

This would also use Lookup from Glide Big table (In My case) when it tries doing the lookup from the Previous table.

As I need to fetch JSON from previous table. Still gives the warning of more than 100 rows thing.

Regards,
Dilip

Hi Guys,

I could just create JSON Object. I can pass it via template column but it still constructs only particular ROW’s JSON.

But how can I get a joined List without using Joined List computed column to get all available rows JSON?

Regards,
Dilip

Hi Guys,

Any advice on this.?

Thank you in advance

Regards,
Dilip

Hi Guys,

For now I am creating a big table which will have details required to be sent out to API.

Meaning there will be two tables one normal and one big table.

When I write data to normal table and submit it’ll write required information to big table for further processing.

This is a wacky workaround. But couldn’t get the JS to work.

is this acceptable workaround?

Regards,
Dilip