Flexmonster Version: 2.8.19
When creating a calculated measure, if the same name is used as an already existing measure then the resulting calculated measure will append a “-2” to the name, but if an additional calculated measure with the same name is added it will update the calculated measure with the “-2”.
Create Calculated Measure with name “Test” -> “Test” created
Create additional Calculated Measure with name “Test” -> “Test-2” created
Create additional Calculated Measure with name “Test” -> “Test-2” overridden.
The our expectation is that if the same measure name is used, it should always increase the appended number OR not allow the user to input calculated measures with the same name. It should not just override Test-2.
Additionally, spaces are valid Calculated Measure names which creates a seemingly blank measure name.
Thank you for posting on our forum.
It seems that the issue with overwriting the calculated measure is not reproducible on the latest version of the component. Please update your Flexmonster to avoid this behavior. Here is our updating to the latest version tutorial for guidance: https://www.flexmonster.com/doc/updating-to-the-latest-version/.
Concerning blank measure names, we want to explain that you can adjust custom validation in order to prevent unwanted naming. We have prepared the JSFiddle demonstrating how to disable “Apply” button if the name only contains spaces or is already present in the list: https://jsfiddle.net/flexmonster/d5r8km2h/.
Please let us know if it works for you.
Looking forward to hearing your feedback.
I am able to reproduce the overriding issue on the latest. I have attached a gif of the issue. Notice how if I add a 3rd calculated measure with the name “Test” it overrides “Test-2”.
We can add the custom validation you provided, but it is unexpected.
There is another issue I would like to confirm. When removing a calculated measure from the fields dialog, all previous added calculated measure and measures are also removed. Is this expected?
Thank you for reporting the issue and for preparing the demonstration. It brought some light to the nature of the problem.
We are going to fix the issue with removing all the calculated measures after removing one of them in the minor update ETA June 14.
Concerning overwriting the calculated measure’s name, we have added this issue to our backlog. As for now, we suggest using the provided validation for this purpose. You can adjust it to fit your needs exactly. Currently, it prevents creating empty and duplicated names.
Please let us know if it works well for you.
Feel free to reach out in case other questions arise.
Thank you for looking into the issue. June 14 will work for us. We will move forward with the custom validation for now.
Thank you again,
We are glad to inform you that both issues with calculated values naming and removing fields when removing calculated measures from Fields List were fixed.
This is available in the 2.9.1 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/.
Feel free to write to us in case of questions.
We are wondering if the recent fix works well for you.
Looking forward to your feedback.
Yes, the calculated measure is now working as expected. Thank you for the fix and response.