Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Access import error: Field 'ENTITLEMENT_VALUE' doesn't have a default value

ekorh
Regular Contributor
Regular Contributor

Hi,

We are trying to run an access import from AAD but keep getting this error for the job:

Field 'ENTITLEMENT_VALUE' doesn't have a default value

Any idea what could be causing this? And how to solve the issue?

Thanks already in advance!

7 REPLIES 7

avinashchhetri
Saviynt Employee
Saviynt Employee

@ekorh,

Are you using the default OOB config for access import or overridden that with your custom configuration ?

Regards,
Avinash Chhetri

ekorh
Regular Contributor
Regular Contributor

Hi,

We are using the AzureAD OOB configurations for ENTITLEMENT_ATTRIBUTE.

But only importing following: AAD group, Team, Channel, Directory Role, Application.

rushikeshvartak
All-Star
All-Star

can you share connection config


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

For entitlement attribute the following:

{
"entitlementAttribute": {
"AADGroup": {
"colsToPropsMap": {
"entitlementID" : "id~#~char",
"entitlement_value": "displayName~#~utf8mb4",
"customproperty2" : "description~#~utf8mb4",
"customproperty7" : "mail~#~char",
"customproperty8" : "mailEnabled~#~char",
"customproperty9" : "onPremisesSecurityIdentifier~#~char",
"customproperty11" : "groupTypes~#~listAsString",
"customproperty14" : "mail~#~char"
}
},
"Team": {
"colsToPropsMap": {
"entitlementID" : "id~#~char",
"entitlement_value" : "displayName~#~char",
"description" : "description~#~char",
"customproperty1" : "internalId~#~char",
"customproperty2" : "webUrl~#~char",
"customproperty3" : "discoverySettings~#~char",
"customproperty6" : "isArchived~#~char",
"customproperty14" : "mail~#~char"
}
},
"Channel": {
"colsToPropsMap": {
"entitlementID" : "id~#~char",
"entitlement_value" : "displayName~#~char",
"description" : "description~#~char",
"customproperty1" : "email~#~char",
"customproperty2" : "webUrl~#~char"
}
},
"DirectoryRole": {
"colsToPropsMap": {
"entitlementID":"id~#~char",
"entitlement_value":"displayName~#~char",
"customproperty4":"description~#~char",
"customproperty8":"roleTemplateId~#~char"
}
},
"Application": {
"colsToPropsMap": {
"entitlementID":"id~#~char",
"entitlement_value":"displayName~#~char",
"customproperty1":"id~#~bool",
"customproperty2":"resourceAppId~#~bool",
"customproperty4":"orgRestrictions~#~boolListInverse",
"customproperty5":"oauth2AllowImplicitFlow~#~bool",
"customproperty7":"createdDateTime~#~char"
}
}

}
}

utf8mb4 is this supported data type ?


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

According to the customer it was introduced to solve a previous problem with some AAD group names.

Please check with Saviynt Operation if any missing patch in your version as its not documented


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.