asked on May 5, 2022
This is a follow up bug from https://www.flexmonster.com/question/bug-hierarchy-levels-are-not-ordered-according-to-result-of-members-request/
As a result of that issue, it was advised to remove the defaultHierarchySortName: 'unsorted' value from the options object.
We've now realized that this leads to an unexpected error: In instances where we have a Hierarchy's Level in either Columns or Rows, the values no longer show.
Specifically, if we have in the Slice something like
```
"columns": [
{
"uniqueName": "Destination",
"levelName": "Region Name",
},
...
}
```
With defaultHierarchySortName: 'unsorted' in Options our report looks like the attached image named with-unsorted-good.png
And without it, it looks like the attached image named no-unsorted-error.png.
⋅ May 5, 2022
Hello,
Thank you for reaching out to us.
We haven't managed to reproduce the issue on our side. Please check the following JSFiddle: https://jsfiddle.net/flexmonster/wzLensv4/
In the example above, we tried to recreate your data structure and configurations. It seems that everything works as expected. Could you please modify that sample to show us the described issue? It would greatly help us.
Looking forward to hearing from you.
Kind regards,
Nadia
