techgy wrote:I was hoping that the latest release would have addressed an issue that I'd reported a while back. When an event is scheduled on any given day and resources are assigned to it, I get a message that reports a conflict in resources except that the conflict is on an adjacent day.
Case in point. The General RS Broadcast on a Saturday in September will use the chapel, overflow, and the cultural hall (for a dinner afterwards). The next day - Sunday is Fast Sunday for our stake and I get a conflict between the two events. I've already reported this and verified that the entries are correct.
Is anyone else seeing this?
The resource scheduling tests for possible conflicts. It then reports both "resource conflicts," which are hard conflicts; and "Events at other locations." The first category seems to work reliably (except for one case I'll mention later). That is the most important situation, since it prevents you from double-scheduling a resource. I have not seen hard conflicts reported for an event on another day. Is that the kind of conflict you're seeing in the specific case you mentioned?
The possible conflicts for "Events at other locations" do seem to look more broadly than is necessary; they look at adjoining days, which doesn't seem necessary, and although they do advertise that they are looking at events which are scheduled for different resources, it seems more annoying than helpful to show so many events that aren't really conflicts. Perhaps if it were labeled more clearly it would be less annoying -- for the first section, make it clear that these are hard conflicts that will stop you from scheduling on top of an existing reservation; for the second section, make it clear that these are some other events that are okay from a resource perspective, but might possibly involve some of the same people, who can't be two places at the same time, or may be frustrated that they are involved in events on consecutive days.
The one case that is a problem with hard conflict checking concerns changing a single-day event to a repeating event. If you have scheduled a resource for a single-day event and then later decide that it needs to be a repeating event, when you try to save those changes, you are told that the resource is already scheduled for that first day and so you can't save your changes. Well, duh! Of course it's scheduled for that day -- I'm the one who scheduled it. I just want to extend that schedule to multiple days in the future, of which the single day is just the first instance. I have reported this bug. The good news is that this problem doesn't occur when you are adjusting an existing repeating event -- just when you go from single to repeating.
Questions that can benefit the larger community should be asked in a public forum, not a private message.