IdentityNow Delimited File Source: Does Account Schema HAVE TO be same as what columns exist in the file?

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Say you have a file like this:

H1,H2,H3,H4,H5
U1a,U1b,U1c,U1d,U1e
U2a,U2b,U2c,U2d,U2e

And your schema only has:
H1,H3,H5

Then an aggregation in IIQ works, but it fails on IDN. Unless the source feed is updated to remove H2 and H4 columns, an aggregation does not go through. Why is that? Why does IDN require a modification of the incoming feed if we were to only pull in certain fields and not all, from a particular file. I can think of ways using a build map rule to ignore the fields not required, but why is it not a simple OOTB feature?

2

Yes, I replicate your scenario and it fails. Never tested this :slight_smile:

Maybe because it is not actual aggregation, it is just file import. End result may be same for us but technically may be it is different expecting all the schema attributes as columns. Or maybe some setting is there ?

Alternative you can look into SQL loader connector, see if that fits your requirement.
Integrating SailPoint with SQL Loader

2 Likes
3

@MVKR7T Possible. Let’s see if we can get an expert to answer this

4

IDN aggregation will always fail if the column headers don’t align with the schema. Unfortunately the error isn’t very descriptive to this issue, but using the “Upload Schema” option you can overwrite the schema without doing it manually field by field. The obvious downside - be sure you want to do this before just updating it.

I’ve seen HR change file formats without communication both intentionally and accidently so knowing what the format should be is critical to knowing if the schema should be changed.

5

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.