Mimicking the deprecated selectRecordsAsync() beha...

[Claire_Conza]

Hi

This has worked for me for over 18 months and now it fails. The code is within an automation script block. The code window shows a strikethrough line in “selectRecordsAsync” and the tip suggests this method is deprecated.

Any ideas why and what alternative I have please?

let mgl_allocationsBase = base.getTable(“allocations”);
const mgl_allocationsBaseRecords = await mgl_allocationsBase. selectRecordsAsync();

Thanks

Claire

[JonathanBowen]

Hi @Claire_Conza - if you scroll down a bit further on the pop-up you will see the deprecation notice:

So your script will continue to work for now, but will fail at some point in the future. You can future proof it now by passing in the fields you need:

let table = base.getTable('Table 1');
let result = await table.selectRecordsAsync({fields: ['Name', 'Notes']});

Have a look at this post too, which passes all fields easily:

Mimicking the deprecated selectRecordsAsync() behavior Scripting app

You’ve probably all seen the following warning by now: [image] 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 …

[Steven1]

const table = base.getTable(yourTableName), fields = table.fields.map( f => f.name), query = await table.selectRecordsAsync({fields})

this little snippet was gold 

Thank you!