Hierarchy member import - bug?
SummaryHierarchy member import - bug?
In our hierarchy, we have multiple levels. If we include all levels of data in a single import file. Some of them will fail. Please refer to the following for the detail,
Here is the import data,
|tree structure||tree code||parent party id||party id|
It seems to me that if parent party id/party id combo (200 & 400, 300 & 500) is imported before combo (100, 100 & 200, 100 & 300) is imported, the import for 200 & 400, 300 & 500 will fail.
I wonder why we do this validation (parent level record needs to be existed before child level record import) in hierarchy member since what we care about is the party IDs.