Use case:
Make it possible to book in multiple bookings in the future using the same contributing service (Demodulator chain)
When these bookings are 1 hour apart from each other (a gap of 1hour in between) we want to create a new contributing booking (the demodulator chain) otherwise we will reuse an existing one.
For the booking name we use the selected Demodulator.
Problem
We noticed that the service of the contributing booking is already generated when the booking is.
This is causing the 2nd booking (with 1h gab) is failing because a service with the same name is already present on the system.
Question:
How can we make sure we can achieve our use-case? We like to keep the booking name nice and readable.
For contributing bookings the service is indeed created when the booking gets converted to a contributing resource. Using the same name will also create the resource with the same name, so I'd suggest using a clear base name for these bookings and add a suffix to distinguish each occurrence.
To make things more clear visually, you could make use of custom properties. These can be shown using Block Info and applying a custom column configuration.