Better document (inline in the app) the LDAP location sync

[UserGoodtm]

Good afternoon. I have already encountered this error several times. When syncing with LDAP, users reset or change its location. And when you notice this problem, it's too late to roll back the update because of the new assets you've added.
Now we have to check all users and return them to the correct location.
This probably happened first in 8.0.4, but I noticed the same behavior in 8.1.3, when I had a massive change in user properties.

[UserGoodtm]

I think I understood what the "error" is... since I did it "correctly" before, I didn't immediately understand what the problem was. You don't need to set the location (1) before synchronization (2)

Perhaps it is worth somehow "protecting" from this in the future? It is possible to add information that adding a location will affect all users.. or something similar to avoid a massive change.

[uberbrady]

Ah, yes, that one very often ends up leading users astray.

It's tempting to just get rid of it, entirely - which has been under consideration.

Or, maybe, to your point - just better-document what it's supposed to do, and when you might want to use it.

[snipe]

@uberbrady If you want to give me the phrasing, I can make sure we have some more useful help text underneath that.

[uberbrady]

Generally, this is probably not going to do what you want. This setting makes it so that when you synchronize your users from LDAP, all of them will be assigned the given Location. This is usually not what you want.