Prevent change of fields due to synchronization when running a Update/Notify Users job on a set
When updating one user manually, we get a notice where we can confirm that some fields (amongst others: campus, rs libraries and user group) are not to be overwritten by the next user synchronization.
When updating users in a set running the Update/Notify Users job in Alma, the same choice of prevention is not presented. Hence leaving some fields to be changed back in the next synchronization.
We experienced this running a job changing campus, RS library and user group on a set of users. The first two fields did not change back in the synchronization. The latter did.
Would it be possible to have the same choice of prevention running a job on a set as we do when updating one and one user?
This time we had to change manually nearly 500 users. We would very much like to spend our time and resources on more fruitful work in Alma and in the library.
Best,
Ann-Louise Skjager
Special librarian
Oslo Metropolitan University
Ann-Louise
shared this idea
Running the Update/Notify Users job with ‘Added/changed field’ set to ‘Internal’ makes the user group/title/campus changes not be overridable by the SIS load.
-
Hi,
Running the Update/Notify Users job with 'Added/changed field' set to Internal seems to make the user group/title/campus changes as not overridable by the SIS load. Is that not your experience ?
-
Sandra Morgan
commented
I agree there should be an option to protect fields when running jobs. I've also noticed that if you have to 'toggle' the user's Account Type, any added internal manual notes are changed to 'external data' when the account is toggled back to an 'external account'.
-
Dan Michael O. Heggø
commented
Quite sure the "protect certains fields from being overridden" property isn't exposed to the Users Api either. Seems a bit ad hoc.