I am having trouble setting up the Resources for our desired functionality.
The goal is to have 3 services available with capacity for 2 distinct appointments each, but with the condition that different services cannot overlap. So if Service A has been booked for a day, then a second booking for that day can only be another Service A booking, and not Service B or C. Note that the two distinct appointments (so they can partially overlap) is a requirement for our needs.
For proof of concept I tried to configure this for only 2 services, but already got stuck there. What I tried was to create several resources shared between different employees, such that if an employee for service A was booked, it would take a resource that it shared with both employees for service B. For example:
- employees A1, A2, B1, and B2, 2 for services A and B respectively, - Resource, unique for the location, shared with services A and B, single location, and employees A1, B1, and B2. - Resource unique for location, shared with services A and B, single location, and employees A2, B1, and B2
It didn't work as I expected: Although booking a service with employee A1 did block appointments with B1 and B2, the same was not the case when a service was booked with A2. Deleting the first Resource did make A2 bookings block appointments for B1 and B2. It seems that only 1 resource is being taken into account.
Is this a bug? Is there a different way to get the desired result?
Hi,
I am having trouble setting up the Resources for our desired functionality.
The goal is to have 3 services available with capacity for 2 distinct appointments each, but with the condition that different services cannot overlap. So if Service A has been booked for a day, then a second booking for that day can only be another Service A booking, and not Service B or C. Note that the two distinct appointments (so they can partially overlap) is a requirement for our needs.
For proof of concept I tried to configure this for only 2 services, but already got stuck there. What I tried was to create several resources shared between different employees, such that if an employee for service A was booked, it would take a resource that it shared with both employees for service B. For example:
- employees A1, A2, B1, and B2, 2 for services A and B respectively,
- Resource, unique for the location, shared with services A and B, single location, and employees A1, B1, and B2.
- Resource unique for location, shared with services A and B, single location, and employees A2, B1, and B2
It didn't work as I expected: Although booking a service with employee A1 did block appointments with B1 and B2, the same was not the case when a service was booked with A2. Deleting the first Resource did make A2 bookings block appointments for B1 and B2.
It seems that only 1 resource is being taken into account.
Is this a bug? Is there a different way to get the desired result?
Kind regards