Thanks!
That doesn’t entirely answer my question and I had read the documentation.
To recap, I’ve a CSV file with usernames, email addresses and some profile information. When I import that the first time, all accounts are created and passwords are created.
If I import that file a second time, then it seems from testing and the documentation that the passwords are reset. I want to import that a second time and more because some data may change, some records may be added and so on. But, while I do want to update the user, I don’t want to reset the password.
If I add a password column to the CSV with a value then when I do the second import it would reset the user password to the initial value even if they’ve changed it. That’s not really what I want.
If I set the password column in the CSV to blank, then what? the initial import or the later one with new records creates accounts without passwords? That’s what the documentation seems to say. That’s also not really what I would want.
The options on the first tab are confusing as there’s no clear precedence, ie
Update existing users?
Update roles for existing users?
If we say “no” to updating existing users, does that mean roles for existing users are not updated or does that boolean take precedence over the first?
And, if those two options acknowledge the design point that users can be updated in part, ie profile information updated but not the role if we answer YES then NO to those questions, then a third option “Update passwords for existing users?” would logically fit as well.
The CSV I have contains membership information for an association, members have different levels which can change so I do want to repeatedly import the same users. Most of the time, I want to update users rather then add them.
I hope I’ve explained that properly!
