Accessories checked out to locations block the new Scope Locations feature

[FabioGomes35]

• Running two Snipe-IT instances; 8.1.2 for testing and 8.1.3.
• RHEL 9 & nginx
• Bug found on On Admin Settings > Update General Settings > Scoping > Scope Locations with Full Multiple Companies Support
• Not possible to reproduce on the demo
• No manual edits done on the database

Cannot enable the Scope Locations with Full Multiple Companies Support option since it is greyed out. I'm running a separate instance on 8.1.2 with a backed-up db to be able to access the conflicting location count and figure out which items/actions trigger change.

Although the conflicting items have been resolved, the count remains high at ~100.

However, checking accessories in and out to a location adds and subtracts to the count ( I confirm that the accessories' companies are the same as the locations' companies ). Also, after ticking the Scope Locations with Full Multiple Companies Support option and then checking an accessory out to a location, it will grey out again. This does not happens with assets, only with accessories.

Thanks in advance!

[DRLDN-Admin]

In Admin Settings > Update General Settings

✅ “Full Multiple Companies Support” can be enabled
❌ “Scope Locations with Full Multiple Companies Support” remains greyed out with the message:
“This option is disabled because you have conflicting locations set for 1 or more items.”
This happens even though all prerequisites are met, so it appears to be a logic/UI bug.

Diagnostics Performed:

1. Locations all have company_id ≠ NULL
2. No locations used by multiple companies across items (Assets, Accessories, Users, Components, Consumables)
3. All mismatches between item and location company have been resolved
4. Soft-deleted (deleted_at IS NOT NULL) rows for users, assets, accessories, components, consumables, and licenses have been checked and corrected
5. No soft-deleted licenses with company_id exist
6. Soft-deleted models exist, but models are not location-scoped
7. .env settings validated and loaded
8. Caches cleared (php artisan config:clear, etc.) and IIS restarted
9. .env includes:

• MULTI_COMPANY=true
• SNIPEIT_COMPANY_ENABLED=true

10. No Laravel or dropdown-related errors in storage/logs/laravel.log
11. Upgraded from v8.1.15 to v8.1.17 via Git, including migrations and dependency install — issue persists

Expected Behavior:
The Scope Locations… toggle should be enabled when all scoping conditions are satisfied.

Actual Behavior:
The toggle remains disabled with the “conflicting locations” message despite no conflicts present.

Attachments / Additional Info:

• Screenshots of the disabled toggle
• Console logs show no errors
• All SQL verification queries return no rows

[bzeus]

Still working on reproducing

[bzeus]

I can confirm that I am getting the same results. The toggle remains disabled.