Hi, I have a customer who is trying to sync users to a Division called "Contact Centre".
We have configured a custom mapping under the Azure section "Provision Azure Active Directory Users" but the users are not syncing to the correct division. The settings we have used in the Genesys Azure app are:
Mapping Type: Constant
Constant Value: Contact Centre
Target Attribute: urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:division
Match Objects Using This Attribute: Yes
Matching Precedence: 2
Apply This Mapping: Always
Something that might make this slightly more confusing is that they have changed their default Division from "Home" to "Contact Centre".
The only way we could get users to sync was to create a new division called "Home", so it looks like there is a settings somewhere that is forcing users to always go into a Division called "Home".
Any help on getting this custom mapping to work would be greatly appreciated.
The target attribute urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:division should be working.
We have tested this with Azure and the only issues seen was a common problem we have been seeing that Azure will ignore extension attributes on the initial user sync, even when their logs say they are syncing them. We found the values were not actually in the payload sent. However when this happens it usually sync the values correctly on the second pass against the user.
Do your audit logs show that a sync was attempted with the attribute?
Does the log show any error?
If there are no errors an the sync can be confirmed in the log, then the best next step would be to open a support case.
StatusCode: BadRequest Message: Processing of the HTTP request resulted in an exception. Please see the HTTP response returned by the 'Response' property of this exception for details. Web Response: {"status":"400","scimType":"invalidValue","detail":"Division name 'Home' does not match an existing Division.;\n contextId:[ 2fcdf05a-9af0-48c8-8071-e4e05b3f8545 ]","schemas":["urn:ietf:params:scim:api:messages:2.0:Error"]}. This operation was retried 0 times. It will be retried again after this date: 2021-01-06T13:11:58.5355984Z UTC
I've done some testing and urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:division only works when there is a division called 'Home". If the default Division has been renamed to anything else it does not work.