and more in a single search tool across platforms. Read the announcement here. |
11/30/2023 07:14 AM
Why is it that when an AD import fails, all the customproperties for the entitlements clear and we have to readd the values ourselves? How can we change it so that if an import fails, it won't make changes to the entitlement customproperties? I did check the connection and we aren't importing anything in to those CP's so it's not like they're being overwritten when the connection fails.
Solved! Go to Solution.
11/30/2023 07:50 AM
Hi @IAM ,
Can you share your groupImportMapping json.
11/30/2023 07:51 AM
{
"entitlementTypeName": "memberOf",
"performGroupAccountLinking": "true",
"incrementalTimeField": "whenChanged",
"groupObjectClass": "(objectclass=group)",
"mapping": "memberHash:member_char,customProperty1:sAMAccountName_char,customProperty4:gidNumber_char,customProperty2:cn_char,lastscandate:whenCreated_date,entitlement_glossary:description_char,entitlementID:distinguishedName_char,entitlement_value:nameinnamespace_char,customProperty3:distinguishedName_char,updatedate:whenChanged_date,status:isCriticalSystemObject_char,RECONCILATION_FIELD:entitlement_value"
}
The 2 CP's that were cleared out were CP21 and CP 22, which I don't see in this JSON
11/30/2023 09:12 AM
Hi @IAM ,
As per the documentation CP21 and CP22 are internally used to store values of Group Category and Group Scope parameters that are defined while creating a group in the Create AD Groups page, are used to derive the value of the groupType attribute which is stored in customproperty4.
As per Saviynt suggested, these custom properties must not be used to map or store any other properties. Try with some other custom properties.
11/30/2023 09:27 AM
Ah ok thank you good catch