Hi,
I have an L2 list that is used to capture staging data. The parent to this list is L1.
The user runs a import action via the UX and a csv file to load serial numbers into the L2 list (L2 is a numbered list)
The user has been provided a template to upload the L2 list wherein they need to enter the parent and that is subsequently mapped in the import action. So all L2s end up having legit L1 parents.
In the event the parent does not exist in the system but in the file, the action fails, which is the desired behavior.
But this also consecutively creates a lot of orphans outside the L1 hierarchy since the parent does not exist.
A blueprint of the hierarchy for reference
- L2 child
- L2 child
L1 - L2 child
- L2 child
L1
All (Top level of L1) - Orphan 1
- Orphan 2
- Orphan 3
The idea is to delete these orphans so as to not create unnecessary members in the L2 list.
I went about creating a property module on L2 to identify the ones that do not have an L1 parent. The idea was to use this boolean in deletion that I can run at the very end of the import process.
When I create a property module, all these orphans do not appear in the dimension itself coz of which I am unable to identify them.
Is there another workaround to this?
Thank you very much.