Read custom fields with SCIM API V2

[MarcoDebattisti]

Hello Community,

we rcently migrated IAS from API V1 to SCIM API V2 and we have custom transformations that do not work anymore.

We used to read 2 custom fields in the Source transformations and then we added conditions in the Target transformations, but it seems that the custom fields are not read anymore.

How can we read custom fields with SCIM API V2?

in the Source transformation we added this:

{
"sourcePath": "$['urn:ietf:params:scim:schemas:extension:successfactors:2.0:User']['IASsync']",
"optional": true,
"targetPath": "$['urn:ietf:params:scim:schemas:extension:successfactors:2.0:User']['IASsync']"
},

where IASsync is the technical name of the custom field we have in SF.

then in Target trasnformation we added a condition:

($.IASsync != '2046299')

where '2046299' is the picklist OptionID for the value 'NO'. Previoulsy this worked and users with IASsync=NO where skipped and not synced in IAS, which is our objective.

Any help is appreciated since we are stuck with it!

thanks

[MichaelBuonoGKN]

The name of the field added to the SF User Profile is IASsync? Or are you using HRIS Sync Mappings to move a value from EC into the User profile? I'm trying to do something similar, so hopefully an answer will come along. Meanwhile, I've read that IAS customField0-9 can only be populated using API v2 (SCIM), so I'm somewhat curious how this worked previously if so. https://community.sap.com/t5/technology-q-a/ias-api-how-to-get-custom-attributes/qaq-p/12778321

[MarcoDebattisti]

@MichaelBuonoGKN with sf.api.version = 1 it was working (our scenario is different from yours, I guess).

we added a custom field in SuccessFactors with technical name "IASsync", we added it to sf.user.attributes (userId,username,status,email,lastName,firstName,lastModifiedDateTime,personKeyNav,loginMethod,CustLoginMethod,IASsync) and then read it in the Source transformation with a basic rule:

{
"sourcePath": "$.IASsync",
"optional": true,
"targetPath": "$.IASsync"
},

then in Target transformation we filtered it out with a condition: && ($.IASsync != '2046299')

As a result, SF users with that particular value in that field were not synced to IAS.

Now with sf.api.version = 2 custom fields cannot be read anymore...SCIM API only reads the 'standard' custom fields custom01 - custom15 but our client already used all of them...

We're trying to work with group filters (like: do not sync users assigned to a certain group), but we're not lucky so far...

any thoughts on how to use the condition and which would be the right syntax?

we're trying with ($.groups[?(@.displayName == 'GG-IASSYNC')] EMPTY true) but it does not seem to work

[MichaelBuonoGKN]

You can try to use the [ias.user.filter] property to exclude that population, instead of building it into the transformation code logic.

urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:IASsync ne "2046299"

Or whatever the correct schema is...

More information about all the properties is here: https://community.sap.com/t5/technology-blogs-by-sap/sap-ips-list-of-all-properties-available-for-us...