Save the date! Join us on October 16 for our Product Ops launch event. Register here.
Aug 30, 2021 11:12 AM
You’ve probably all seen the following warning by now:
I’m guessing the deprecated behavior might still work well into 2022, but if you want to future-proof your scripts right now and/or depend on the old behavior, here’s the cleanest, functional way of mimicking it I’ve found so far:
const
table = base.getTable(yourTableName),
fields = table.fields.map( f => f.name),
query = await table.selectRecordsAsync({fields})
This particular destructuring syntax obviously depends on your scope being clean.
But in practice, I’d usually just write this:
const
table = base.getTable(yourTableName),
query = await table.selectRecordsAsync({
fields:table.fields.map(f=>f.name)
})
Either way, I figured I’ll share this and ask if anyone has figured out a quicker method.
Solved! Go to Solution.
Aug 30, 2021 05:09 PM
Hi @Dominik_Bosnjak,
I use the “fields” array directly from the table; there´s no need to “map” the “fields” array.
const Table = base.getTable("TableName");
const query = await Table.selectRecordsAsync({ fields: Table.fields });
Best
Sergio
https://devblocks.agency
If this reply fixed your problem, please mark it as a solution :white_check_mark:
Aug 30, 2021 05:09 PM
Hi @Dominik_Bosnjak,
I use the “fields” array directly from the table; there´s no need to “map” the “fields” array.
const Table = base.getTable("TableName");
const query = await Table.selectRecordsAsync({ fields: Table.fields });
Best
Sergio
https://devblocks.agency
If this reply fixed your problem, please mark it as a solution :white_check_mark:
Aug 31, 2021 05:39 AM
Awesome, didn’t know you could just pass an entire field object like that, cheers.