Leveraging Intelligent Recommendations for Operational Transformation. AMS Partners click HERE | EMEA/APJ Partners click HERE |
10/16/2023 10:12 AM
We created a new AD endpoint, for user account correlation rule we used user company attribute to match with customproperty attribute on the account which caused lot of incorrect mappings.
(users.username) = accounts.name OR (users.companyname) = accounts.CUSTOMPROPERTY27
We tried removing the user account correlation rule, ran account imports but accounts are still correlated to incorrect users
Is it possible to make all accounts orphan and then update user account correlation rule, later run account import jobs or any other options to resolve this issue?
Thank You.
10/16/2023 11:37 AM
@rajsannidhi : There is no straightforward way to do this. We have option to override the correlation as part of import using csv but no option to uncorrelate the user. Since you are in 5.5.x version. Only way I can think of is using custom query job update user_accounts table and make user key as null for such accounts
10/16/2023 12:19 PM
@Saathvik Thank you for the details, yes I tried account upload selecting "YES for Overwrite User Assigned" as below, with blank user owner. It didn't work, tried 'Update & Add' also for operation column
Account Name | owner user | endpoint | operation |
ABCD | XYZ | update | |
XYZS | XYZ | update |
10/16/2023 01:02 PM
@Saathvik joined users table, this also didn't work
Update saviyntaws.user_accounts ua
join saviyntaws.users u on ua.userkey = u.userkey
join saviyntaws.accounts a on ua.accountkey = a.accountkey
join saviyntaws.endpoints ep on a.endpointkey = ep.endpointkey
set ua.userkey=null
where ep.endpointkey IN ('63')
and a.accountkey IN ('172811')