Script Button to archive a linked record

[Matthew_Billiodeaux]

Hello,

I am trying to create a button that moves a record reference in a table from one field (“User”) to another field (“Archived User”). I noticed this can be done without scripting through Fibery’s no-code automations, but, there is a conditional that I need built into the button:

 if (User!=""){
      ... }

This is the code I have so far:

const api = context.getService("fibery");

for (const entity of args.currentEntities) {
    const UserIds = await api.getEntityById(entity.type, entity.id, [["User"]]);
    if (UserIds != null) {
        await api.updateEntity(entity.type, entity.id, { "Archived User": UserIds });
        await api.updateEntity(entity.type, entity.id, { "User": "[]" });
    }
}

And that code is throwing this unexpected exception…

Failed to execute action "Script": field.toLowerCase is not a function

Any help is appreciated!

Disclaimer

I am new to Fibery, and I know there may be better ways to structure my app, but please note my main purpose of posting this is to focus on learning the API/scripting portion of Fibery.

I have read these so far to construct the above code:

• [✔️ DONE] Duplicate a record - #7 by Polina_Zenevich
• Action buttons (old) | Fibery Help Center
  ** i know I probably should have read this one instead but didn’t find it until recently: Automated Action Buttons (new) | Fibery Help Center
• fibery-community / Action Buttons · GitLab
• close-task-and-all-subtasks/readme.md · master · fibery-community / Action Buttons · GitLab
• Fibery API
• And though only tangentially related, this is listed also as it was extremely inciteful reading, the Fibery founders thoughts on low-coding automation… https://fibery.io/blog/automations-concepts-overview-for-no-code-tools/

---

[Oleg]

Hi, Matthew

Thanks for letting know about your problem. Please find below explanation

1. Let’s assume I have setup with two users for entity as you described above. Every feature can have one User and one Archived User
   

   

2. This is how the button script action can be configured to move User to Archived User
   

   

The code is

const fibery = context.getService('fibery');
for (const entity of args.currentEntities) {
    const entityWithExtraFields = await fibery.getEntityById(entity.type, entity.id, ['User']);
    if (entityWithExtraFields[`User`].id) {
        await fibery.updateEntity(entity.type, entity.id, {
            'Archived User': entityWithExtraFields[`User`].id,
            'User': null
        });
    }
}

Please let me know if I didn’t catch the issue correctly.

Thanks,
Oleg

[v3j]

What do I need to study to learn how to create such scripts?

[Oleg]

Hi, @v3j

We hope that there will be no need to learn scripts in the nearest future. No-code applications should make the life simpler. Will do our best to accomplish that.

Thanks,
Aleh

[v3j]

Hi Oleg,

No worries! I’m just really interested to learn how while waiting What google keyword would you suggest for starters?

[Oleg]

Hi, @v3j

Thanks for your question. You may try suggestions from how to become javascript developer - Google Search

Good luck,
Oleg

[Matthew_Billiodeaux]

Hello Oleg, and thank you for the reply. Very clear, and concise. Thanks for the included premise/assumption + picture + code. Also, apologies for the delayed reply. I work on this project in my spare time.

Regarding this assumption: Every feature can have one User and one Archived User…

I should have mentioned in my first post earlier that there can be multiple users for “UserIds” field. I see now that my naming convention is also misleading… I will update the original post! Sorry for the confusion!

[Matthew_Billiodeaux]

I ended up just restructuring my table and avoiding the whole array issue. thanks for your help!