bldg scheduler can't edit other stake's reservation where 2 stakes use same bldg

davidltuck · #1

The agent stake's ward building scheduler is not able to edit and change a reservation entered by the non-agent stake's ward building scheduler. The understanding is that any building scheduler should be able to change any reservation and schedule details.

#2

It is correct that any building scheduler for a location should be able to edit any reservation or event that uses resources at that location.

Could you provide some more details about what the agent ward building scheduler is seeing and what happens when he/she tries to edit the reservation?

#3

After further investigation I don't see how there can be a building scheduler from any unit not in the agent stake. The agent stake designates the building schedulers and the membership of another stake, even if they are sharing a building of the agent stake, is not available from which to select an individual as a building scheduler. It is just not possible to designate a person outside a stake's membership to be a building scheduler.

It is possible that the stake of the unit sharing the meetinghouse location created a location with the same name as a location in the agent stake and designated a building scheduler for that location. These are two different locations in the calendar system. The building scheduler from the agent stake will not have access to the location in the non-agent stake. However, if the agent stake has set up the shared meetinghouse location correctly the sharing unit from the non-agent stake should be able to see that location and all events with resources scheduled. But I suspect they have not.

What may have happened here is that both stakes have a meetinghouse location with the same name. The non-agent stake's location should not exist and is giving the sharing unit the wrong impression that they are scheduling events at the shared meetinghouse location when they are not. Only the events and reservations made at the agent stake's location are valid.

The agent stake needs to include the sharing unit to the list of units that have rights to use that location and the sharing unit's stake should delete the location they created.

rootbeericecream · #4

from the "non-agent" stake (me) -- we used to have a duplicate location entry , but that has since been deleted. The event in question was created on our non-agent stake calendar, and specified the agent-stake location/resource. The event was visible on the agent resource calendar, and the non-agent event calendars -- so the proper location is being used.

The problem is that only the original non-agent stake submitters approvers/editors can edit the event. Any attempt by the agent-stake building scheduler to modify event location/resources is unsuccessful.

#5

So the issue reported by davidtuck in the opening post to this thread is not really the issue. The issue is that the agent stake's building scheduler for the location cannot edit events made by the sharing stake, or the sharing unit of the sharing stake. The second part of the issue is the members of the sharing unit or sharing stake cannot view events at the location because the location does not appear in "Available Locations". Yet when the sharing unit or stake creates events on a sharing ward or stake calendar the agent stake location is available to allocate resources.

This other thread is a better discussion of the issue.

davidltuck · #6

The inability of the agent stake administrator or building scheduler to modify an existing reservation on the reservation page...

I find that I am able to drag and drop the event to a new time slot while in the weekly view without any problems. But when clicking to edit reservation details and making changes in the Start and End dates/times followed by an Update Event click are not saved even though the message reports success. In addition to failing to change times of the reservation, changes to different rooms are also not saved.