Aggregate entitlements endpoint doesn't allow wrapping data in double quotes

[wtboice (William Boice)]

The new entitlement aggregation endpoint that replaces the deprecated CC version does not allow us to wrap data in double quotes like the CC version did.

I have commented here on this issue.

POST /api/source/loadEntitlements

I have the need to INCLUDE commas within the data that I am delimiting. On the CC API I was able to wrap this data in double quotes. The new API does not seem to support this functionality. Initially if I have the initial columns wrapped in quotes, I get a 400 error as seen below. If I remove the quotes from the column names, and leave the data wrapped in double quotes I get a 500. Is there a way to use a different delimiter? Is there a way to include comma’s in my data? { "messages":…

I am also surfacing it here for more awareness.

[colin_mckibben]

Hi William,

Thank you for submitting this. Engineering has opened a ticket (IDNARC-2846) to track the work on this. They agree that this functionality should exist in the new endpoint.

[colin_mckibben]

@wtboice can you please provide a sample CSV file that is causing this error?

[wtboice (William Boice)]

Colin,

I just tried this again, and it appears to be working. I am validating against the source api as well.

[wtboice (William Boice)]

@colin_mckibben This appears to be working for both entitlements and for source uploads for CSV.

[dmbrown1386 (Derek Brown)]

@colin_mckibben, quotes in the column headings are still causing our aggregations to fail using the new endpoint. Below is a screenshot of the error I get in WindowsPowerShell:

But I can send the exact same file to the CC endpoint without issue. I can even use the file to update the schema using the “beta/sources/ID/schemas/entitlements” but when I send that same file to the new Endpoint I get the above error. The file is created using the Export-Csv command which in WindowsPowerShell wraps everything in quotes, regardless of the Delimiter used.

My current workaround is using the ConverTo-Csv and Out-File commands with some Encoding options set. But none of this is required for the new Load Accounts endpoint.

[wtboice (William Boice)]

@dmbrown1386

@colin_mckibben, quotes in the column headings are still causing our aggregations to fail using the new endpoint. Below is a screenshot of the error I get in WindowsPowerShell:

But I can send the exact same file to the CC endpoint without issue. I can even use the file to update the schema using the “beta/sources/ID/schemas/entitlements” but when I send that same file to the new Endpoint I get the above error. The file is created using the Export-Csv command which in WindowsPowerShell wraps everything in quotes, regardless of the Delimiter used.

My current workaround is using the ConverTo-Csv and Out-File commands with some Encoding options set. But none of this is required for the new Load Accounts endpoint.

I did the same.

My workaround is:

$hashtable | Export-Csv -path $groupexport -NoTypeInformation -append
#fix for sailpoint new endpoint.  IT won't accept quotes in the header line
$groupHeaderStrip = get-content $groupexport
$groupHeaderStrip[0] = $groupHeaderStrip[0]|% {$_ -replace '"',''} 
set-content $groupexport $groupHeaderStrip