AzureAd Import Access Error

[sandeepverma]

Hi Team,

We see an issue during full import of access for AzureAD. Job is failing due to below error.

Connection Name: AzureAD Recon

Job Name: AAD_Access_Import

Error: "Data truncation: Data too long for column 'CUSTOMPROPERTY6' at row 1"

After that, we remove all the CP 6 mapping from connection but still we see the same issue.

Replication Steps:

> We have mapped entitlement attributes mapping in ENTITLEMENT_ATTRIBUTE.

> Connection Name: AzureAD Recon

> Job Name: AAD_Access_Import

> We Try to run job to import the all access using full import

Thanks

[DaanishJawed]

Hi,

have you removed customproperty6 from Entitlement Attribute JSON at the connector level and tried?

Raise an FD ticket since this looks like an issue with Datatype of customproperty6.

[SB]

@sandeepverma 

This is happening because the CP6 attribute can only hold 256 characters. AAD has a default mapping also defined in code and the data imported from AAD is more than 256 for 1 of the Entitlements attributes. This issue is fixed in the latest release and you can check with the Support team/CSM to get the fix.

Alternatively you can try to map CP6 with any other field which does not have large data.

[Sheba]

Hi Sahil,

we are using 23.0 latest version, still we have this same issue. for an alternative option do I need to change the CP6 value to some other CP for all the entitlement types which are in entitlement_attribute json?

Thanks

Sheba

[SB]

You will need to update CP6 for all entitlements type to another unless you are aware which type has a value larger than 256 character. 

CP1 to 5 are of longtext type for now and you can check for your environment specific from Data Analyzer as well. 

- Navigate to Admin>Admin Function>Data Analyzer.

- Expand entitlement_values and hover to the i icon corresponding to the column you want to check

[flegare]

Hi @SB ,

Is the best way to get this done to open a FD request or can we get this done ourselves through SQL update?  We are having the exact same issue...

Thanks!

Francois

[SB]

You can change the mapping of the attribute from UI itself under ENTITLEMENT_ATTRIBUTE param. 

[flegare]

Thank you, I had thought of this option.  Is there any plans on fixing those cp fields lenght in a future release?  It feels strange to have to adapt ootb configuration for such a reason

[DaanishJawed]

Hi @flegare ,

Please raise this as an enhancement. CP1 to CP5 are currently long text.

Thanks.

[flegare]

Hi @DaanishJawed ,

The ootb Saviynt-provided mapping for an onboarded application does not match the definition of the data available in the target application.

Is this really an enhancement or is it a good candidate for a support ticket?

Thanks!

[DaanishJawed]

Hi @flegare ,

This is an improvement and hence will be an enhancement.