Sometimes you need to modify a lot of existing data, either a static modification or by csv field matching.
I am running into this now - i need a way to set a new field for over 900 records.
Agreed, when testing, it’s a common need to add some junk records, reset to see empty states, etc. A truncate option would make testing workflows much easier. Egor Kunovsky is it possible to upload an empty CSV as a workaround? I could see keeping a testing set of data in one CSV and a “truncate” (empty) CSV per table being useful. These would be similar to other frameworks which have conventions for seeding a database and resetting it.
Ian Miller: yes, this sounds like a plan, thanks
This might be a useful hack meanwhile - Bulk operations and Timer Tricks, part 3: mass update for the records
Great workaround posted by Victor here Bulk operations and Timer Tricks, part 3: mass update for the records
Just a kind update to push this item as we don’t have any sustainable workaround to bulk update records and it’s a recurrent need.
- Adalo API doesn’t allow to bulk update from external tools like Integromat (we can update only one record at a time)
- As Victor said, the workaround based on the countdown timer is good for a few records but not for hundreds of records as Adalo uses the client side capabilities (the user smartphone). It’s much too slow and doesn’t work well.
Thanks
Now you don’t need any workaround to trigger actions in bulk because Hidden Trigger is here! Check out its features:
-
Create automated actions that run in the background
-
Connect with lists and set up delayed actions
-
Execute actions in bulk without showing them to end users
Streamline your app’s functionality with seamless background operations.
Buy Now - https://components.theuncoders.com/