Automation: Getting the most recent Rec using script
The script looks to be using what I would consider outdated technique which we can argue, why ChatGPT is using var instead of let or const, or is using for() instead of .filter(), .map(), .reduce(), forEach(). and why it's also using .then instead of await.
I think this is the problem with ChatGPT, in that, if users haven't run through enough of the subject matter to know right from wrong, what's old technique, what's modern technique, what's common technique and what's preferable technique - it might actually compound your learning of the subject.
Not to say that there isn't a million ways to do the same thing in JavaScript. ChatGPT is powerful though, and where I would then take the conversation from your sample script, is ask it to use an await, and tell it to use .filter(), .map(), forEach(), or .reduce(), and ask it why it's using var instead of const or let declaration. You need to call it out as you start to understand the structure of code - and surprisingly, in many cases it will correct these problems and give you legit/healthier looking code.
But anyway, I digress - back to focusing on your actual problem! 😂
Within an Automation Action itself, you'll see there's the ability to add input from other previously run actions, such as your Find Records, or the Trigger itself. You can then uses these inputs within your Automation script accessing then through the input.config() function.
My example below shows you an easy way to take those inputs values, and by using the JavaScript destructuring technique, assign them directly into their own self-named variables.
Inputs are a great way to get started with Automation Scripting. I've personally found a couple of limitations with them however, where I prefer to use API calls to find the data that I'm needing in my Automation - where typically I'll only grab the Trigger record input, but not any other data, or at least, I'm very selective with what data I draw-in to my script via input.config() - there are pro's and cons, it will all depend on your project. Mostly, input.config() will typically do what you need it to do for you.
Thanks for all the help. I'm still at a loss on what to do.
I've got this script from the examples:
// the table to check
let table = base.getTable("Stays");
// the record we're searching for duplicates of.
// we need to create a 'recordId' input variable connected to a record trigger
let config = input.config();
let recordId = config.recordId;
// the field to save duplicates in. this should be a self-linked record field
let duplicatesField = table.getField("HAID");
// query the table and find our record according to its id:
let query = await table.selectRecordsAsync({fields: []});
let record = query.getRecord(recordId);
// search for duplicates
let foundDuplicates = query.records.filter((potentialDuplicate) => {
// if they're the exact same record, they're not duplicates:
if (potentialDuplicate === record) {
return false;
}
if (potentialDuplicate.name === record.name) {
// if the names match, we've found a duplicate:
return true;
}
return false;
});
console.log(`Found ${foundDuplicates.length} duplicates of ${record.name}`);
// save the duplicates:
await table.updateRecordAsync(record, {
[duplicatesField.name]: foundDuplicates,
});
Maybe I need to create a field with the record ID in it? Maybe then I don't even need a script like @kuovonne said.
