🍉 Meet Flexmonster Pivot Table & Charts 2.9.Check out all hot features!
Get Free Trial

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

Answered
Marleze Potgieter asked on September 22, 2020

When creating a pivot, adding a calculated field, and these by default is added to the bottom of the Values.
When you view the pivot with the calculated fields in the default column spot the field values are calculated correctly.  Please see screenshot ‘create_pivot’
When you click on Fields and move the calculated field (in my case named ATP) higher up.  See screenshot ‘values_order’
When you then view the modified pivot, the values are not re-calculated , see screenshot ‘edited_pivot’  Instead in my case the values displayed for ATP is the ‘Aggregated Basic Concession Cost Net’ value.

17 answers

Public
Mykhailo Halaida Mykhailo Halaida Flexmonster September 24, 2020

Hi Marleze,
 
Thank you for reporting this – we’ve managed to reproduced similar behavior on our side.
 
Our development team will take a look at this – the fix will be available with our upcoming release ETA Nov 2nd.
 
Please let us know if you have any other questions we can help you with in the meantime.
 
Best regards,
Mykhailo

Public
Mykhailo Halaida Mykhailo Halaida Flexmonster October 23, 2020

Hi Marleze,
 
We are happy to inform you that the issue with mixed-up values of calculated measures has been fixed – we’ve managed to solve this a little bit earlier than the previously provided ETA.
 
This is available in the 2.8.18 version of Flexmonster: https://www.flexmonster.com/release-notes/.
 
You are welcome to update the component. Here is our updating to the latest version guide for assistance: https://www.flexmonster.com/doc/updating-to-the-latest-version/.
 
Please let us know if you have any other questions we can help you with.
 
Regards,
Mykhailo

Public
Mykhailo Halaida Mykhailo Halaida Flexmonster November 3, 2020

Hi Marleze,
 
Hope you’re doing well.
 
Just checking in to ask whether you’ve had a chance to check out the recently introduced fix – is it working well for you?
 
We would be happy to hear your feedback.
 
Best regards,
Mykhailo

Public
Marleze Potgieter November 3, 2020

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!

Public
Mykhailo Halaida Mykhailo Halaida Flexmonster November 4, 2020

Marleze,
 
Thank you for the heads-up! We will be looking forward to further updates.
 
Kind regards,
Mykhailo

Public
Marleze Potgieter November 13, 2020

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

Public
Mykhailo Halaida Mykhailo Halaida Flexmonster November 16, 2020

Hi Marleze,
 
Thank you for your detailed response.
 
So far, we haven’t been able to reproduce the described behavior on our side.
 
In order for us to investigate this further, do you think you could provide us with your report configurations together with a dummy data set with which such behavior is reproducible? This would greatly help us get to the core of the issue faster.
 
In case any sensitive data is involved, you can send it to us via email to ensure privacy.
 
Looking forward to your response.
 
Best regards,
Mykhailo

Public
Marleze Potgieter November 17, 2020

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

Public
Mykhailo Halaida Mykhailo Halaida Flexmonster November 19, 2020

Marleze,
 
Thank you for providing us with a descriptive sample.
 
We can see the described behavior is reproducible – the predefined calculated values are not available when the corresponding property is set inside the Global Object while left unspecified inside the Report Object. Our team will take a look at this, and we’ll return to you with a fix on ETA Dec 14th.
 
However, it seems like the three issues you’ve reported in your previous response extend a bit further than this. If this is the case, we would appreciate it if you could provide us with samples for those use cases as well, as we haven’t been able to reproduce them so far.
 
Looking forward to your reply.
 
Best regards,
Mykhailo

 

Public
Marleze Potgieter November 19, 2020

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. 
 
 

Attachments:
Report.json

Public
Mykhailo Halaida Mykhailo Halaida Flexmonster November 20, 2020

Hi Marleze,
 
Thank you for providing further details on the issues in question.
 
We were able to reproduce the first scenario thanks to the provided sample – this bug has been added to the list of issues to fix by Dec 14th.
 
Speaking of the report file you’ve attached, we could not connect Flexmonster to your cube – we assume it has restricted access configured on your side. Therefore, it would indeed be great if you could provide us with a dump of your cube so that we can restore it on our side – please let us know if there is any progress on this! 
 
Also, it seems like the “Save As” tab is your custom toolbar button – do you think you could share its handler function with us, just in case it contains anything that might be related to the issues we’re discussing?
 
Looking forward to your response and have a great weekend ahead!
 
Kind regards,
Mykhailo

Public
Will Liu November 22, 2020

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
 
 
 

Public
Mykhailo Halaida Mykhailo Halaida Flexmonster November 23, 2020

Hi Will,
 
It is nice to meet you, hope you’ve had a great weekend as well!
 
Thank you once again for providing the samples and explaining the issues you’ve encountered.
 
The situation now seems clear to us – the described issues are most likely related. With that in mind, our team will take a look at this, and we’ll return to you with the results on the previously specified ETA of Dec 14th.
 
Please let us know if there is anything else we can help you with in the meantime.
 
Regards,
Mykhailo

Public
Mykhailo Halaida Mykhailo Halaida Flexmonster December 15, 2020

Hi Will,
 
We are glad to inform you that the issue with setting properties for SSAS through the global object was fixed.
 
This is provided in the 2.8.22 version of Flexmonster: https://www.flexmonster.com/release-notes/.
 
You are welcome to update the component: https://www.flexmonster.com/doc/updating-to-the-latest-version/.
 
Please let us know if everything works fine for you.
 
Best regards,
Mykhailo

Public
Mykhailo Halaida Mykhailo Halaida Flexmonster December 22, 2020

Hi Will,
 
Hope you’re doing well!
 
Just checking in to ask if you’ve had a chance to try out the latest fix we’ve introduced. Have you found it helpful?
 
We would be happy to hear your feedback.
 
Kind regards,
Mykhailo

Public
Marleze Potgieter December 22, 2020

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!

Public
Marleze Potgieter January 22, 2021

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

Please login or Register to Submit Answer