I am having an issue with delimited file sources where the data imported is not accurate after being exported. I’m indexing my User ID column and all single value columns have the correct number of rows and are accurate. However my multi-valued columns do not seem to always index to the User ID column.
Are there any further behaviors to be aware of when using delimited file sources? I have tried three different datasets and have the same issue with them all. Is there a limit to the number of multi-valued columns? There are more rows exported than imported and I thought that using the User ID column as the index would require a 1:1 relationship with all other columns in the row. Am I incorrectly understanding this?
Thank you for posting and welcome to Developer Community.
For multivalued attributes in delimited file, IdentityNow creates a single entry in CSV for each attribute value assigned.
For example, if you have groups (multivalued attribute) and the account has 2 groups assigned, i.e, HR and Payroll.
There will be two entries in csv with one entry for HR and another entry for Payroll in the name of same User ID.
There is no hard limit to number of multivalued attributes.
What you are observing is correct and expected behaviour of IdentityNow.
Thank you for your reply. If one of the multi-valued attributes has subgroups would you create another entitlement type and change the schema to have a child hierarchy? Do you know if child hierarchies are supported on a delimited file source? Is it a requirement to list entitlements on the entitlement type only or can they be in the account schema?
I have tried both with no luck and cannot find a tutorial or anything more in depth than the article in my original post which doesn’t specify whether using the entitlement type is a requirement.