How to deal with appointment series

I have an event app and some appointments happen once and others regularly (e.g. every Tuesday from 12:30 - 14:00). To maintain the events, I have always made a CSV export, copied the serial dates x times (e.g. 8 times for the next 8 weeks), incremented the date by 7 days each and then imported the data again. I bet there are cleverer methods for this. Any ideas? Many thanks in advance!

so many

are there timeslots ?

I have approximately 10 - 15 appointment series in completely different timeslots, like Monday 20:00 - 22:00, Tuesday 12:30 - 14:00, Wednesday 09:00 - 16:00, Friday 09:00 - 10:00, Saturday 10:00 - 11:00, Sunday 09:00 - 10:00 etc. Happening every week. And I am tired of “copy & paste”… :wink:
I have the following ideas:
1.) Using external database (e.g. Airtables) and have scripts/automation on that to copy datasets and adjust the dates. Or
2.) Have a form where I can load a dataset and create a new one on the basis of the old dataset including date + 7 by pressing just one button
Any other ideas?

we can still use adalo collection

Hi Andy @Andy74,

Unfortunately Adalo doesn’t have any built-in ways to automate bulk operations with records (creation, update, removal).
Some of the possible workarounds are:

  • use countdown timer tricks (e.g. my old video here for bulk update https://youtu.be/0OLszLhb_7k). Creating records is also possible with timer, you’ll need some kind of “template records” collection. Downside of countdown timer - it works ok for small amount of records
  • use Adalo Collections API to create records from some 3rd party platform (e.g. Make). This works pretty well, except that you have to pay for the plan which has Collections API and also you’ll have to pay for 3rd party platform.
  • use custom component (I remember someone mentioned it exists but can’t find any now).
  • use external collections to store records and use automations on their side (Airtable, Xano, Supabase, …).

Hope this helps.

Best,
Victor.

Ok. Great! Thank you. That should work. I think I go for a variant of your 1st workaround.

1 Like

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