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?
Yes, I replicate your scenario and it fails. Never tested this
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 ?
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.
