Bulk Create Database Entries


I currently building an app that showcases gym workout programs, and then allows individuals to ‘subscribe’ to them and then schedule them in to their own calendar.

So far I’ve been able to create a system that sees a single workout (within a group called a ‘program’) being ‘scheduled’ by creating a record in a ‘scheduled workouts’ database, which references back to the original workout (as well as the user, and the chosen date for this workout.

What I want to do is bulk create ‘scheduled workouts’ for all the workouts in a given ‘program’. These would be done using the chosen start date and the ‘day of workout’ being added together to procedurally create the date for each workout.

The best I can do is create a screen where a user can click on each workout one by one to create individual ‘scheduled workouts’. What I want is a ‘schedule all’ action.

Pretty certain this can’t be done in Adalo alone. Zapier doesn’t appear to do procedurally created records. Can anyone recommend a solution, native or 3rd party, that could fulfilled this automation?

Hey @liam.m.day welcome to the forums!

You are right that this cannot be done in Adalo alone at the moment. There is a feature request for this right now which you can find here: https://ideas.adalo.com/feature-requests/p/cron-or-something-like-it

However, I do think this can be achieved in Zapier with their own internal integration “Schedule”: https://zapier.com/apps/schedule/integrations

Colin, thanks for the reply. Timing tasks is not the issue that I was stuck with. The problem I was trying to overcome was creating a series of database entires based off of the values in a particular field of another database.

I have now overcome this with a less elegant workaround - rather than trying to create an action that will create X amount of entries based off of values Y, I have created multiple create actions with a condition that checks the number of variables in Y. I did this by mirroring the multi reference field for a series of single reference fields, each with its own create action.

While this creates a fixed limit of how many database entries can be generated, it has removed the need for an external workaround.

Thanks for the help!

Oh, I misinterpreted what you wanted but it’s clear now based on how you solved it. Glad you got it working!

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.