When using the manual mapping mode, the structure is built based on value, label, key and parent key.
the hierarchy is built based on the structure of Key <- Parent Key and is independant of the label structure.
When we use the new CheckBox Tree with a mapped datasource, the hierarchy is built based on the label structure (Label <- Parent Label ), the value is a unique ID and the keys don't appear.
While the manual mode is great and flexible, the mapped mode is not that easy to handle.
Could you make the mapped mode being structured like the manual mode, please.
This threw me for a loop as I was trying to understand how the new component works. I was trying to use the manual example for implementing mine using a mapped datasource and it didn't make sense. Your post helped me figure it out!
basic Bill of Material use case :
i.e. : an assembly can use several spare parts and this assembly can be used in several finished products.
I have to use this assembly several times in the tree but I must display the same label
If I understand correctly, the core of the issue is that the new component requires each Label to be unique in order for Parent label to retain referential integrity. And @cvo - you're running into a use case that requires duplicates, which would be possible using keys instead of labels?
Yes, that's it : multiple parallel hierarchies can contain same elements or even parts of a treelist.
This is the case when you handle a BOM or a general ledger.
This capability makes the difference between an ERP and a solution that can only handle project management and CRM.
I guess this is why newcomers over the last 2 decades didn't succeed to replace ERP leaders like SAP or Oracl.,They just neglicted this feature.
So please, take the time to improve the treegroup, table and sankey chart components in the way they manage hierarchies.
