Changing Maximum Number of Attendees back to 1

Frequent Visitor

I changed the maximum number of attendees from 1 to 5. It won't let me now change it back to 1. The lowest it will go is 2.

I have tried "Inspect Element" to change the min number from 2 to 1. This allows me to use the down arrow feature to lower it to be 1. However, the change won't save and it reverts back to 2.

Also using inspect element to change the number directly to 1 also doesn't work.

8 Replies
@l_christensen1085 I'm having the same issue. Have you found a solution for this?
Thank you.

Last week I couldn't set it to lower then 2.
This week I can't even change it.

 

Edit: When I edit the HTML and remove the disabled="" attribute from the field, I can edit and the setting gets saved. Microsoft only releasing untested alpha software recently. Annoying...

@O___O  @l_christensen1085 Thanks for reaching out to us. Any service with maximum attendee as 1 is a single customer service and any service with maximum attendee as 2 or more is a multi customer service. As by design, we cannot convert single customer to multi customer or vice versa. Hence we cannot edit and save a number less than 2. You can create a new service for such scenario. Thanks for your interest in Bookings.

@Radhika_Khetan_MSFT  If the number of attendees implicitly decides what type of service this is, then it's the wrong way to go. This is bound to raise confusion.

 

It would be better if you clearly advertise a service as a single-attendee or multi-attendee service and let the user explicitly decide what kind of service he wants to create.

 

To quote the Python philosophy: "Explicit is better than implicit".

 

But, that aside, I believe this is bad practice. Why can you lower the attendee number from 1000 to 2, but not from 2 to 1. I understand that you said in the backend are single- and multi-user services. But this seems very arbitrary. Programmatically, it makes no difference: if (Current attendees < Max attendees) then it is bookable, else it is not bookable. The current user experience is horrible.

@Radhika_Khetan_MSFTAre you open for feedback? I'd love to hear your opinions on my recent suggestion.

@O___O ,

 

I can confirm what @Radhika_Khetan_MSFT said is accurate based on my experience.  If your Booking service's "maximum attendees" is EVER saved to 1, then you can NEVER change it to anything else.  If your service's "maximum attendees" is EVER saved as something !=1, then you can NEVER change it to =1.   If you want to switch between !=1 and =1, you literally have to delete and recreate the service.

 

I don't understand why MS purposely implemented this "feature"!

This is a stupid limitation that should be invisible to end users.

 

If there are two separate event types in your backend, why don't you automatically create a new single invitee event, clone all the information from multi booking to standard, then delete the original rather than just create more work for the end user?

@Radhika_Khetan_MSFT 

This is absolutely, unjustifiably insane behavior from a company of your size and reach. Wow. I'm honestly floored. 

 

I'm now going to have to recreate 50 services because we didn't realize that 2+ would not put customer details into the calendar invitations, just a message that says “This is a multi-customer booking. Login into Bookings….etc.” which is also poor functionality in its own right, though potentially justified. 

The two issues together plus little guidance from MS are going to cost me many hours. Ouch.