[midPoint] How to deal with duplicate unique attributes?

[Ethan Kromhout]

I have a situation that is similar, though perhaps not quite the same, 
where one of my source systems has multiple accounts for some users. In 
my case there primary and secondary accounts for some users, and then 
sometimes accounts can be considered inactive. I used the method 
discussed here 
https://wiki.evolveum.com/display/midPoint/Multiaccounts+HOWTO 
<https://wiki.evolveum.com/display/midPoint/Multiaccounts+HOWTO> to 
create tagged shadows for each of the accounts, then in schemahandling I 
select the primary account record to store in a user attribute that I 
use later in correlation.

I can share some config snippets if the multiaccount approach sounds useful.

Thanks,

Ethan

On 10/20/20 2:57 PM, Gus Lou via midPoint wrote:
> Hi Guys
>
> Has anyone here ever had to deal with unique attributes (dupplicate) 
> from the HR base?
> I explain, in my human resources system the same person can have more 
> than one record, with the status of hired and fired.
> When I run the synchronization task, the MP displays the error of 
> unique attribute value 111.111 is not unique in Data.csv
> I would like to apply some kind of filter to process only the record 
> with hired status in case of duplicate records.
>
> I am studying the information on Correlation Expression to try to 
> achieve this goal
> https://wiki.evolveum.com/display/midPoint/Correlation+and+Confirmation+Expressions 
> <https://wiki.evolveum.com/display/midPoint/Correlation+and+Confirmation+Expressions>
>
> Best Regards
>
> Gus
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> https://lists.evolveum.com/mailman/listinfo/midpoint
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20201020/71f99f80/attachment.htm>