Asset location changes after LDAP sync – all assets incorrectly set to last manually synced location

[ColaMix]

Description:

Since the last LDAP synchronization, the location of assets in the inventory management system has changed unexpectedly. Specifically, all assets are now assigned to the same location (e.g., Straubing), which appears to be the last location that was manually synced.

This issue is reproducible:
If the last manual sync was done with "Landshut," then all asset locations are set to "Landshut." The problem seems to persist across syncs and does not reflect the actual assigned locations from LDAP.

We attempted a quick update to version 8.1.6 of the inventory management system, but unfortunately, this did not resolve the issue.

Steps to reproduce:

Perform a manual sync with a specific location (e.g., Straubing).

Run LDAP sync.

Observe that all asset locations are overwritten with the manually synced location.

Expected behavior:
Each asset should retain its correct location from LDAP after synchronization.

Current behavior:
All asset locations are overwritten with the last manually synced location.

Environment:

Inventory Management Version: 8.1.6 (updated, issue persists)

LDAP sync configuration unchanged

[uberbrady]

That feature definitely does work weirdly. We should either pull it entirely, or re-work it so that it does what the user is actually expecting. Maybe with better help text? Or the option to specify a particular Base DN?

If we did the latter, we might be able to be able to load up the suggested OU from the Locations table (for the Location-specific OU).

[ColaMix]

As shown above, the location for the assets is incorrect.

But if I go directly to the asset, it looks like this:

Default location is incorrect in this case
Location is correct. as it should be.

One wonders, what is the default location? Where the assets are added to the inventory or where they are collected when not in use? The headquarters of the company? Be that as it may, in the overview as above it would be logical to see the location where the device is currently located, i.e. where it was issued. This is not correct.

anyway

maybe it's also because our number of users probably exceeds 999. That could also be a problem. We also leave deactivated users there so that we can track who had which hardware if nothing comes back.

Translated with DeepL.com (free version)

[snipe]

Default location is wherever the device lives when it's not currently checked out to someone. Maybe a closet somewhere, a warehouse, the main IT office, etc.