This was a protection to stop users from moving a record to a different branch/location once it already has dependent records ("children") attached to it. We have event templates and activities and reservation records tied to a branch. It seems now that is the wrong approach. Instead, all of those records needs to be able to move around to different branch locations. I am closing this ticket and will work through solutions as we revise how branches behave in the app.
Log in to comment and vote
Comments1
David Aidekman
Jul 12
This was a protection to stop users from moving a record to a different branch/location once it already has dependent records ("children") attached to it. We have event templates and activities and reservation records tied to a branch. It seems now that is the wrong approach. Instead, all of those records needs to be able to move around to different branch locations. I am closing this ticket and will work through solutions as we revise how branches behave in the app.