cancel
Showing results for 
Search instead for 
Did you mean: 

IPS - saving a custom attribute

MarcoDebattisti
Participant
0 Kudos
2,242

Hi,

we are live with IAS with SuccessFactors as Source system and IAS as Target system.

We have a requirement to save custom attribute 2 in IAS with the user id and a prefix 'HI_'.

I added custom transformations in the Source system like this:

{

"sourcePath": "$.userId",

"targetPath": "$['urn:sap:cloud:scim:schemas:extension:custom:2.0:User']['attributes'][1]['value']",

"functions": [

{

"type": "concatString",

"prefix": "HI_"

}

]

},

{

"constant": "customAttribute2",

"targetPath": "$['urn:sap:cloud:scim:schemas:extension:custom:2.0:User']['attributes'][1]['name']"

},

Then I added the following custom transformations in the Target system:

{

"sourcePath": "$.userSysID",

"targetPath": "$['urn:sap:cloud:scim:schemas:extension:custom:2.0:User']['attributes'][1]['value']",

"functions": [

{

"type": "concatString",

"prefix": "HI_"

}

]

},

{

"constant": "customAttribute2",

"targetPath": "$['urn:sap:cloud:scim:schemas:extension:custom:2.0:User']['attributes'][1]['name']"

},

when I run a sync job, all employees are ending in error when writing to IAS, with this error:error=com.sap.security.iag.provisioning.mapping.exceptions.InvalidJsonContentException: Source path: $.userSysID is not available in content, but is required in defined system transformation Caused by: com.sap.security.iag.provisioning.mapping.MandatorySourcePathNotFoundException: Source path: $.userSysID is not available in content, but is required in defined system transformation Caused by: com.jayway.jsonpath.PathNotFoundException: No results for path: $['userSysID'],
The good thing is that the custom attribute 2 seems filled in correctly:

but I am not able to save it, for sure something wrong in the target transformations.

Any help that you can give me is appreciated!

thanks

Marco

View Entire Topic
MarcoDebattisti
Participant

Hi,

I think I managed to sort it out 🙂

I removed the custom transformation in the Source system and just left the standard one for userName:

then I added this custom transformation in the IAS Target:

seems to work:

there are still a couple of things that I need to verify but seems promising!

Marco

dsouzadylan44
Explorer
0 Kudos
Hi Marco, were you able to get it working with userid feild?
ahonsheng
Explorer
0 Kudos
Hey Marco, I'm current stuck doing the same process as you but instead of $userName as a source im using workforce SCIM API custom fields. have you done something similar?