Values displayed are incorrect if you change the order of the Value columns in Fields Modal

Hi Mykhailo,  We've planned to update to the 2.8.18 version of Flexmonster in the next 2 weeks.
I will definitely let you know once I've tested the fixes.  Thanks for following up!

Hi Mykhailo,  I hope that you are well?
I've tested the fix and I can confirm it is working, however I have a couple of findings:

1. Where you have a Pivot which was an existing (before the fixed FlexMonster version) with calculated fields. 
   • The calculated fields no longer exists for this pivot when you open it. 
   • ERROR TypeError: Cannot read property 'Ub' of undefined is logged in the Console when you open the pivot
   • The pivot opens 'blank', the data only appears when you do one of two things:
     • Resize the DevTools pane
     • Click on the Fullscreen button 
   • I've attached screenshot Scenario_1 & Scenario_1_1 for this example.
2. The above scenario does not happen when you use 'Save As' to create a copy of this existing pivot, then the fields are displayed when you open the (new copied) pivot (of course the calculated fields are still missing in this case.)
   • See screenshot Scenario_2
3. When you add a calculated field, in this case it does not matter if you have the original or the copied pivot open, the calculated field is added to the Pivot and you can move it around and the original issue we reported of moving the columns around seems to work.  But when you save the pivot, the calculated field disappears and can not be found at all, in screenshot Scenario_3_7 the calculated fields before used to "disappear" and we found then at the bottom of the All Fields list, but this time it's not to be found there. 
   • See screenshots Scenario_3 to Scenario_3_7

I hope this is informative, let me know if you need any more information from our side.
 
Thanks, Marleze

Hi Mykhailo,
I've asked my team to investigate, as we can definitely replicate this issue every time on our end. 
If you look at https://jsfiddle.net/0Lb94nyg/ , the following is commented out by default: 

  /*report: {
     options: {
      calculatedValues: true,
      showCalculatedValuesButton: true
    }, */

the same variables are also set here under Global from what we can see:

var pivot = new Flexmonster({
  container: "pivot-container",
  componentFolder: "https://cdn.flexmonster.com/",
  toolbar: true,
  global: {
    options: {
      calculatedValues: true,
      showCalculatedValuesButton: true
    }
  },

When the Report section is commented out, the calculated fields do not appear, but when un-commented the Report section, then the calculated fields are displayed.
If this does not help, we can look at sending you guys some sample data to try and replicate this issue on your end.
Thanks Marleze

Hey Mykhailo,
The following JSFiddle demo https://jsfiddle.net/yq29gw84/3/ replicates the first scenario mentioned:

• ERROR TypeError: Cannot read property ‘Ub’ of undefined is logged in the Console when you open the pivot

I also got the report JSON for the particular pivot which seems to be problematic, attached if that will help you guys.
The 'Formula #1' is the calculated field that disappears when the pivot is closed & re-opened (after you Save or even Save As the changes made to the pivot) 
We're trying to figure out what the best way is to give you guys a copy of our cube and config to the pivot that we're experiencing this with.  But I hope the above helps. 
 
 

Hi Mykhailo,
 
I'm Will, Marleze's coworker. Hope that you had a great weekend.
 
I'll try to explain the issue we are facing in these three scenarios that Marleze described above.
 

1. Loading an existing report with calculated values will end up having error 'ERROR TypeError: Cannot read property ‘Ub’ of undefined' thrown and blank page. This can be replicated by  https://jsfiddle.net/yq29gw84/3/ , which is confirmed by you as a bug. 
2. 'Save As' will drop any calculated measures in the report when scenario 1 happens. This 'Save As' is our custom toolbar tab which calls 'flexmonster.getReport()' under the hood. That is to say, after loading an report with calculated values, flexmonster.getReport() will return a report without any calculated values. This is a demo based on the first one:  https://jsfiddle.net/e9jrtbL5/1/
3. You can add calculated values after flexmonster loads and flexmonster.getReport() works fine as well. But when you call flexmonster.setReport(flexmonster.getReport()) those calculated values will disappear. I guess this is the same issue as the first scenario? 

Can you please confirm if these findings are related to each other or if there is something else that causes our problems? Please let us know if it has any new conclusions. 
 
Thanks,
Will
 
 
 

Hey Mykhailo,
Apologies, we missed your previous 2 messages.  We will update and get back to you.  Today will be our last working day for 2020, so we will get back to you early 2021.  
Thanks!

Hi Mykhailo, just confirming that we've tested the fix and we're happy that it's working as expected! Thanks.