rservations

[dattels]

One ward posted an event. Then another ward posted an event to the same day, same hours and the system took both events. I thought the system was suppose to prevent duplications. Both of these events are showing up in the reservation calendar. I tried to post another event on the same day and same hours as a test and the system accepted the event. How are duplications prevented?

Thank you - Arlene Dattels

[Gary_Miller]

As long as the events are using different resources/room in a location the event can be scheduled at the same time. Also you can book an event using "no location" or "other location" you could book an event at the same time as well.

[russellhltn]

As Gary says, as long as these are events (not reservations) and are using different rooms and/or different locations, then the system will allow it.

[drepouille]

Several stake auxiliary leaders ask me to post events for them. One reason I usually decline such requests is because, as an administrator, I am able to create conflicting events. Other users without administrator privileges are not allowed to create conflicting events, unless of course they specify "other location" or "no location".
Dana in Omaha

[russellhltn]

as an administrator, I am able to create conflicting events.

If you are a Building Scheduler then you can create an event that conflicts with the intent of a Reservation. But you still should not be able to create conflicting events.

Edit: Also, you can always make a reservation that "conflicts" with an event. That's normal.

[mnmpeterson]

I'm an administrator and a building scheduler but when I tried creating a repeating event at the location I'm a scheduler for it wouldn't let me because of a couple of days where there was a conflict. Rather than allowing me to go ahead and create the repeating event and then delete it on the two conflicts, I had to create multiple events to get around the days when there was a conflict.

So apparently it blocks administrators/schedulers from creating conflicts on repeating events.

[jdlessley]

So apparently it blocks administrators/schedulers from creating conflicts on repeating events.

I'm sure you are verifying the expected behavior. For the benefit of others reading this thread I will restate the programmed behavior.

This is the expected behavior when speaking of events, regardless of who creates the events. The other expected behavior is that a reservation can be created by a building scheduler on top of an event, or an event created by a building scheduler on top of a reservation.