...
The Custom Settings can be created as Formulas and get the data from the custom setting directly.You will find out why soon!
This is because if you EVER need to change the External Services Spec you can’t do it if it’s referenced in a Flow or any version of a Flow. So it’s easier to just delete the link to the Subflow, update the External Service and the Subflow and plug in the Subflow again.
...
I don’t need to set manual variables for the Output
Create an Assign Element to Assign the Output from the Create Calendar Action
To set the Variable for the output you need to traverse through the External Services model
I Output the Long URL as the CalendarURL, the UniqueKey and the CalendarID (I need the CalendarID to create the Event or edit the Calendar later).
For the event I don’t need to save anything but I will set up the Flow to Output the Event ID, Event URL and Unique Key just in case.
...
The users will have the option to delete the calendar and start again if needed.
| Tip |
|---|
To create the Calendar then update the Parent Record, and then create the Calendar Events in the same Flow I had to put a Commit in after the initial update and before the External Services callout for the Calendar Event. This is the Commit Action that I used. (Or you could break it up into two Flows). |
End Result
Unfortunately I can’t show you the final result as it’s in a client’s org but it is a really cool Flow that steps them through inputting custom things like the name of the Calendar and the name of the two Events, then creates the Calendar and the Two events, updates the Parent Record, then links that Parent record to a whole heap of other records to say “this is the correct Calendar for this record”. There will be 100 or so Calendars created in the first batch. Once they are all created we will send out comms to say “hey, here’s your new calendar for 2022 - subscribe here”, and they will get the link to their customised calendar.