scorch29 wrote:One thing that doesn't make sense that I could perhaps still be misunderstanding is if the member for whom I created the reservation for decides to create an event from that reservation they will not be allowed to do so, correct? Given the rule that events cannot overlap each other (for the same room and time).
You can't create a reservation for a person; you can only create a reservation for a unit (ward, stake, or the special "Blocked"). But if you created a reservation for a unit, then a person in that unit who is a calendar editor or administrator will indeed be able to schedule an event on top of that reservation.
Scheduling an event on top of a
reservation is precisely the reason reservations were created -- to allow only members in the specified unit (or a building scheduler) to create such events (and no one else). The "rule that events cannot overlap each other" applies only to events overlapping other events, not events overlapping reservations.
scorch29 wrote:If that is true why allow reservations to overlap at least without giving a warning that there is a potential conflict. I didn't get any warning of a potential conflict.
Reservations can't overlap each other -- if you try to do that, you'll get an error message and be unable to save the overlapping reservation. But as I said earlier, reservations and events can indeed overlap each other. That is not considered a conflict, since a reservation does not actually book a room. Only an event can book a room. So there's no conflict (potential or actual) when an event and reservation overlap (unless, of course, a non-scheduler is trying to create an event on top of a reservation for a unit he does not belong to).
Questions that can benefit the larger community should be asked in a public forum, not a private message.