Mass inactivate users through People Import
Hi
Due to an issue a while back, we had to run an emergency iPaaS job to activate all users. Now, we'd like to selectively inactivate users who are no longer employed or are students. I've tried to create a People Import spreadsheet using only the columns that I think are required for updating. But the People Import process has complained on the Security Role ID and Company fields, even though the sample spreadsheet says they are only required to create accounts. I populated those fields and set the Active column to FALSE. The flag is set to -i, --allowIsActiveChanges. We got the process to run. It shows the accounts were modified, but it didn't inactivate the accounts. I just ran a small test but we'd like to inactivate approximately 8,000 of 42,000 records. Any ideas on the minimum columns needed and why the accounts didn't get inactivated?
Thanks
Answer (1)
Hello Chuck,
The page at TDAdmin > Users & Roles > Import Jobs > [Help button] states the following for the Security Roles column:
* Values in this column are always validated for users of type User, even if the user record already exists. Therefore, even though the data is not going to be updated for existing user records, a valid security role must always be provided for records of type User. This column should always be mapped if your data includes records of type User as this is a required field if a new User records needs to be created.
Futhermore, this column will only update existing records if you have specifically included the AllowSecurityRoleChanges=true flag when submitting your import file to the API. If you have not done this, no changes will be made to the security role on existing records.
Similarly you do have to supply the Organization column for Users. It is validated in error messages as Company, but the two are the same field.
Refer to that page of the TDAdmin interface for the list of minimal required fields. They will tell you if they are always required or just required if mapped/included in your file.
Sincerely,
Mark Sayers
Sr Support Consultant, CS