asked on October 27, 2020
Perhaps a bug? Please see attached description with pictures.
Summary - A calculated measure works fine without a 'Mapping' associated to it, but it adds its own mapping which makes it not work right.
⋅ October 28, 2020
Hello, Eric!
Thank you for posting to our forum and for providing a file.
Please kindly note that the mapping should be used for the fields contained in the data source. For the calculated value, the caption should be specified in the measure object, as it is shown in the first image in the file you sent.
To see all properties that can be defined for the calculated value, we suggest browsing this article.
Please let us know if it helps and if any other questions arise.
Best regards,
Milena
⋅ November 5, 2020
We found that when the uniqueName is different from caption in the calculated measure, the unique name would automatically be injected into the Mapping. Once we set those values to be the same, it worked fine.
⋅ November 11, 2020
Hi, Eric!
We are glad to hear that the issue is resolved.
The detailed description of the component behavior regarding the caption of the calculated measure was very helpful.
Our team has managed to reproduce it on our side. The corresponding task has been added to our backlog.
We will let you know in case there are any updates on this.
Do not hesitate to contact us in case any other questions arise.
Kind regards,
Milena
⋅ November 13, 2020
Hi Milena,
We also faced this issue, step to reproduce
1. create a pivot with mapping object
2. add a calculated value, after that edit the calculated value and rename it.
3. getReport from pivot and setReport the same report.
the calculated values are 0
⋅ November 16, 2020
Hi, Ravi,
Thank you for the steps to reproduce.
Indeed, this is the same issue that Eric had.
We would like to inform you that the fix is going to be provided with a minor update ETA Dec 14.
Do not hesitate to contact us in case any other questions arise.
Best regards,
Milena
⋅ December 15, 2020
Hello Eric and Ravi,
We are happy to let you know that the issue with saving calculated values to mapping was fixed.
This is available in the 2.8.22 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.
Kind regards,
Milena
⋅ December 24, 2020
Hi!
Our team was wondering whether the recent fix helped.
Could you please let us know if everything works fine?
We are looking forward to hearing from you.
Best regards,
Milena
