Using toggle component to create and delete data in the DB

[Modusgot]

What’s up,
I would love to use the “Toggle” component in a list to add and remove items in the Database (DB).

My problem is that I can add data (rows) in the DB but I cannot delete if the user turns off the “Toggle”.

I’d like that if a user turn off “toggle”, in DB delete automatically row (Ord Paises Usua, for example):

[EdU]

this might be what you are looking for
https://help.adalo.com/action-basics/creating-an-action-that-triggers-data-edit

[zmack]

I have the same issue. Can add a record but not delete the same record, because the Collection doesn’t show up in the UI. Is this a known bug?

[Victor]

Hi @zmack,

In order to delete a record, the component needs to have an access to it, i.e. Current Record must be available (on the page or from the list).
In your case, when you add a Toggle, of course you can create a new record. But how can Toggle know that there is a Current record which should be deleted (and also, from where it can take this record?). When a Toggle appeared on the page, there was no record in question.

In such cases a workaround could be using 2 icons instead of toggle, wrapping 2nd icon into the list and and having a conditional visibility on both.

• 1st icon will serve for the state when the record is not created. Visibility condition should be set properly (I can’t say in details as I don’t know the criteria in your case), e.g. Collection_Records → Count, where [condition] is equal to 0.
• For example, if you have a collection of Events, and you are creating an Event with the name “ABC”, the condition is set to Events → Count where Event Name = ABC is equal to 0. This means that the icon will be visible when there is no event with the name ABC.
• Add an action to the icon to create new record (from the example: new Event with name ABC).
• Then you add a 2nd icon, and convert it to a List. In our example, it’ll be a list of Events, where Event Name = ABC. So this list (and the icon) will appear only if there is a record with this name.
• And finally, you add the action to the 2nd icon (inside the list), which is Delete Current Event (from our example).

The resulting logic is: 1st icon appears when there are no events with the name ABC. User clicks on the icon, new Event is created. 1st icon disappears and a list with 2nd icon appears. User clicks on the 2nd icon, the event is deleted, list disappears and 1st icon appears.

Please keep in mind that because of how Adalo works the speed of how it works can be not very fast (app sends a request to the backend and receives a reply, and only after that the visual elements change). So some UI workarounds might be needed to mitigate these delays.

Best,
Victor.