Hierarchical data seems to break if you use same `dimensionUniqueName` on hierarchical value and non hierarchical value, depending on which appears first in defining JSON-object.
2 fiddles to demonstrate the issue:
https://jsfiddle.net/s4ht2qpn/ this works (“Folder” appears in fields view and hierarchical value is working)
But if I re-order the JSON to define string-type after level-type
https://jsfiddle.net/bq8kgf5w/ now “Folder” is gone and hierarchy level2 is gone.
Thank you for reporting about the problem.
Our team will investigate the issue. We will provide you with results ETA May 04.
Please contact us in case of additional questions.
We are glad to announce that the issue with `dimensionUniqueName` in the mapping object was fixed.
This is available in the 2.8.6 version of Flexmonster: https://www.flexmonster.com/release-notes/.
You are welcome to update the component.
Here is our updating to the latest version tutorial for guidance: https://www.flexmonster.com/doc/updating-to-the-latest-version/.
Also, please note that the way to define multilevel hierarchies has been changed. The current structure is described in our documentation dedicated to `mapping` object.
You are welcome to check out an example demonstrating the recommended approach by the link.
Feel free to write to us in case of questions.
We would like to kindly take an interest in whether our fix helped.
Our team is looking forward to hearing from you.