Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
We are manually completing tasks and creating accounts in Saviynt, this is causing accountid to be null. But recon is connected via REST connector, where even if we put keyfield as name, it seems to be checking accountid and since that is null, it is creating a new account on import job.
Thank you for your response. I understand it is not advisable to perform manual provisioning for connected applications; however, the application is only semi-connected. Is there any other solution other than populating accountid in the form as dynamic attribute?
select accountkey as accounts__primarykey,name as accounts_accountid from accounts where endpointkey=1000 and status in (1,'Manually Provisioned') and accountid!=name
Regards, Rushikesh Vartak If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.
Thank you for the workaround. The query had to be modified since accountid is stored as null (not blank). The service lead is checking if we want to go with this.
@NM I will check with the Saviynt Service Lead to provide this detail when she gets into office (Pacific Time) as I am only the middleman to community support requests like this one. She does not usually go much further when there is any kind of solution; but I will ask just the same.
