[bug] Changing location organization does not change the floorplan organization

[purhan]

While registering a new floorplan, there is no choice to select the organization, which infers that it should be the same as the location.

After creating a location (Let's say location_a for organization_a), if we create a floorplan, its organization will also be organization_a

However, if the organization of location is changed (for example, to organization_b) the floorplan will still have the old organization

[nemesifier]

Thanks for opening this @purhan. I think we could assess whether it makes sense to have the organization field on the floorplan or not, probably not, if we can avoid it and modify the code accordingly (also avoiding to generate too many queries) we could solve it this way.

[xoaryaa]

@nemesifier @purhan Hi! I’d like to work on this.

Plan:

• Ensure FloorPlan.organization stays consistent with FloorPlan.location.organization.
• When a Location’s organization changes, bulk-update all related floorplans to the new organization (single update() query, no per-row saves).
• Add regression tests:
  1. create location+floorplan in org A → assert floorplan org = A
  2. move location to org B → assert floorplan org updates to B

If this direction matches, I’ll start implementing and open a PR.

[nemesifier]

@xoaryaa sounds good 👍

[xoaryaa]

Hi @nemesifier @purhan can u take a look at the pr and LMK?