Datasets in REST provisioning JSON

[Amar_Simha]

Hi Team,

We have a requirement to transform one of the downstream parameters that is being updated from Saviynt. We are looking around 15-20 of such mappings and using IF ELSE condition does not seem to the appropriate option.

Just wanted to check, if we can have the datasets which can be referred in the REST connector provisioning JSONs. The dataset mapping can be uploaded but wanted to understand the syntax / reference of using data sets in REST JSONs, specifically during the create / update Account operation.

If not datasets, do we have any other option of maintaining a mapping table / reference in Saviynt?

Please share your views.

[rushikeshvartak]

Dataset is not exposed in REST connector. Create Dynamic attribute and use in REST Connector

[Amar_Simha]

Thanks @rushikeshvartak

We do not have ARS piece as part of integration scope. The Account is to be created as birthright and is triggered by Technical Rules. 

Do we have any other option other than multiple if - else conditions? Also, will there be any performance related impact in evaluating these many conditions?

[rushikeshvartak]

Unfortunately no 

For any desired improvements or enhancements to this process, Saviynt encourages you to submit your proposal through Saviynt's Ideas Portal at https://ideas.saviynt.com/ideas/

Your valuable input is crucial to shaping the evolution of Saviynt systems.

Please notify us once the idea ticket has been created.

[Amar_Simha]

Thanks @rushikeshvartak .

Just thinking, can we make use of the modifyuserdatajson for this use case in any manner? I am assuming it is related to user import via REST connector but wanted to double check the same. 

Please share your views.

[rushikeshvartak]

there you can use dataset tables