Announcing the SAVIYNT KNOWLEDGE EXCHANGE unifying the Saviynt forums, documentation, training, and more in a single search tool across platforms. Click HERE to read the Announcement.

SAP SF Write Back Issue - UPDATEUSERJSON value not found in connection

Sharan
New Contributor III
New Contributor III

Hi ,

Anyone Please help me on this issue,

we are trying to writeBack to SAP SF source system, both email and systemusername. we have defined the UpdateUserJson in SAP SF connection and have created WSRETRY job and gave security system name as empty since it is a source system.

Created a user update rule to create userupdate task and triggered.  task getting created. but not picked up by the job. in the logs we are getting this error,

UPDATEUSERJSON value not found in connection,

 

2022-10-07T08:02:19.961640756Z stdout F 2022-10-07 08:02:19,961 [quartzScheduler_Worker-6] ERROR rest.RestProvisioningService - Connection Failed to LDAP or UPDATEUSERJSON value not found in connection

3 REPLIES 3

SaiSrungaram
Saviynt Employee
Saviynt Employee

To write back information to trusted source like(Successfactors,Workday etc..), we need to create Security System(Attach connection and provisioning connection with your SF or Workday connections, Enable Automated provisioning checkbox) and endpoints. Then run WSRetry Job. Then UpdateuserJSON will pick and will be executed accordingly.

In that case won't the task fail because on that new SS/Endpoint created for SuccessFactor or WD will not have any accounts. Does that mean do we need to configure the aggregation as well for that endpoint?


Regards,
Saathvik
If this reply answered your question, please Accept As Solution and give Kudos to help others facing similar issue.

SaiSrungaram
Saviynt Employee
Saviynt Employee

In this specific scenario, if you observe, we are not even writing any JSON's for account reconciliation or provisioning an account. all we configure in the connector is "ImportuserJson" and "UpdateuserJson". and in the pending tasks, it is "Update user task" is getting triggered,rather than any update account task. Account related task itself wont get generated in this case.

There is no need to do any aggregation/provisioning at endpoint level. But then the question comes like, then why do we need to run "WSRETRY" Job to update user. Here it comes, we use the same job to write back information to trusted source. There are few more restrictions at job level also, we should run WSRETRY Job without adding any specific system, then only task will get picked up to fulfill above usecase.