Error while importing accounts and entitlements for Delimited Source

[sindhu_v_murthy]

Hi Team,

We have created a Delimited Source and are trying to import the accounts on the source.
Schema was configured with following values
UID (marked as Account ID and Account Name),FirstName,LastName,Access.

However while importing the csv file with account and entitlement details below error occurs.
“sailpoint.connector.ConnectorException: Index value for [id] on new object was null.”. Could you please help us with this?

This was working as expected earlier, We observed that Delimited File Source Connectory configurations are updated. We followed all the instructions as per Delimited File Source Connector Configuration.
We are also facing issue with Entitlement import. When ever we import entitlments using Import entitlments it always shows as Group type, due to which we are not able to configure Access Profile.

Please let us know if anyone have any pointers.

[sailajaprathi]

@colin_mckibben Do you have any pointers on this? Is there any recent changes on Delimited Connector?

[colin_mckibben]

I tested this on my tenant and it worked as expected. I used the same account schema as you described.

I uploaded the following CSV file:

UID,FirstName,LastName,Access
1,colin,mckibben,granted
2,john,doe,denied

The account aggregation was successful.

@sindhu_v_murthy, do you see anything different with how I configured it? Maybe your CSV contains an empty value for UID?

[sailajaprathi]

@colin_mckibben It is failing for below, If we wanted to add multiple entitlements

UID,FirstName,LastName,Access
1,colin,mckibben,granted1
1,colin,mckibben,granted2
2,john,doe,denied

[sailajaprathi]

@colin_mckibben Did it worked after changing as above?

Thank you!
Sailaja Prathi

[colin_mckibben]

I did some more testing and here is what I found works.

The account aggregation is looking for a field called id. Since your Account ID and Account Name are tied to UID, the aggregation is failing because it can’t find id. If you change your UID to id, this will work.

accounts.csv

FirstName,LastName,Access,id
colin,mckibben,access1,1
colin,mckibben,access2,1
john,doe,access1,2

I’m not sure if this is a bug or intended. I’m going to ask around internally to see what the expected behavior is. It seems like you should be able to use any name for the Account ID rather than being locked into using id.

[Ajit_Pawar]

Hi,

We are investigating the issue, for time being could you please update source using source API to update the following value:

indexColumn: “UID”

Let us know whether it helps.

Thanks
Ajit

[colin_mckibben]

@Ajit_Pawar, your suggestion to manually update the indexColumn on the source worked. However, it should work automatically with IDN. Please let us know what you find when you investigate.

@sindhu_v_murthy , if you want to continue using UID, you can use the API to manually assign UID as the indexColumn. Start by getting the ID of your source by invoking the GET sources endpoint and finding your source ID in the list. Then, you can use the PATCH source endpoint with the following body to update your indexColumn. Be sure to set the Content-Type header to application/json-patch+json.

[
    {
        "op": "replace",
        "path": "/connectorAttributes/indexColumn",
        "value": "UID"
    }
]

[sailajaprathi]

The issue is fixed on API also.

[colin_mckibben]

The underlying issue should now be fixed. You should no longer have to manually assign the UID as the indexColumn via the API, it should automatically work in the UI.