Dear visitor, despite the COVID-19 outbreak, our team continues operating at full speed.

Also, here is the form where you can apply for a special discount and we will contact you with possible options. Stay safe and continue achieving your business goals.

Fill the form
Get Free Trial
Get Free Trial

[Bug Report] Hierarchy levels are not expanded properly when multiples hierarchies share level names

Answered
Projet TCD asked on April 9, 2020
  • Version: Pivot Table for JSON data sources v2.8.4
  • Browser: All
  • Link to reproduce: https://jsfiddle.net/vuxs3eh4/2/
  • Steps to reproduce:
    • Display pivot table in attached JSFiddle
    • Notice in the Fields configuration that both Fields “Dates > Creation Date” and “Dates > Modification Date” have the same levels (names) “Year“, “Week” and “Day
    • Close the Fields configuration and go back to the pivot table
    • Expend hierarchy to level “Week” on rows “Creation Date
    • Expend hierarchy to level “Week” on columns “Modification Date
  • Observed behavior:
    • Hierarchy level “Week” (and levels below) are not expanded on the columns “Modification Date
  • Expected behavior:
    • Hierarchy levels are expanded properly, even when multiple hierarchies use the same levels names
  • Details:
    • This behavior happens when two (or more) hierarchies use levels with the same names (here “Year”, “Week” and “Day”).
    • In the mappings, the same name is used ‘level‘ since hierarchy levels do not support the ‘caption‘ field.
    • The workaround of naming the levels differently is NOT desired.
  • Proposal:
    • Either the level should be displayed based on mapping property ‘caption‘ (if absent, ‘level‘, as currently)
    • Or the level/parent should be defined based on a new property ‘levelUniqueName‘ (if absent, ‘level‘, as currently)

3 answers

Public
Vera Didenko Flexmonster April 9, 2020

Hello,

Thank you for reporting this issue to us in such detail.

Our team will provide the fix to this problem in the minor release version with the ETA 4th of May.

Please feel free to reach out to us in case any questions arise.

Kind regards,
Vera

Public
Dmytro Zvazhii Flexmonster May 6, 2020

Hello,
We are glad to inform you that the issue with the hierarchy levels not expanded properly was fixed in the latest minor release. You are welcome to update to the latest version to try it.
 
Please note that the approach for defining hierarchies has been simplified. You can see the example here: https://jsfiddle.net/flexmonster/53s1rpfj/.
 
One of the recent improvements is the ability to define a level type. Currently, there is a known issue with the sorting for numeric levels which is going to be fixed in the nearest minor update.
We will notify you when it is ready.
Meanwhile, we recommend using a string type approach described in above JSFiddle.
Please let us know in case of any other question.
Regards,
Dmytro
 

Public
Mykhailo Halaida Mykhailo Halaida Flexmonster May 19, 2020

Hi,
 
We are glad to inform you that the sorting issue with hierarchies that have numeric levels was fixed.
 
This is available in the 2.8.7 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/ 
 
Please contact us in case any questions arise.
 
Best regards,
Mykhailo

Please login or Register to Submit Answer