asked on May 24, 2021
Hello,
We are using Flexmonster with Angular and after upgrading to 2.8.33, we noticed that all of the columns and rows that contain Calculated Values have been suffixed with the "(none)" label. We saw that we could turn off the aggregation labels by setting showAggregationLabels to false within the options object, however, the "(none)" label still appears. We are unable to reproduce it on any jsFiddles, so we were wondering if this was isolated to Angular. We are also using the Custom Datasource API if it makes a difference.
Kind regards,
Henry
⋅ May 25, 2021
Hello, Henry,
Thank you for writing to us.
The issue you describe seems to be related to a recent issue described in the following Support Forum thread.
In that scenario, "(none)" gets added to the measure captions if the "none" aggregation is specified.
Our team will provide the fix to this issue in the minor release with the ETA 14th of June.
Could you please let us know if the "none" aggregation is being used in your case as well?
Looking forward to your reply.
Kind regards,
Vera
⋅ May 25, 2021
Hello, Vera,
Yes, we are also including "none" in our list of supported aggregations in the /fields response. Though, we currently are not aware of anyone using the "none" aggregation and removing it has fixed it for our case.
Thanks much for providing us a reference to that thread!
Kind regards,
Henry
⋅ May 25, 2021
Hello, Henry,
Thank you for your reply.
We are happy to hear that removing the "none" aggregation worked for your case.
Should any further questions arise, feel free to reach out.
Kind regards,
Vera
⋅ June 14, 2021
Hello, Henry,
We are happy to inform you that the issue with the none aggregation appearing in the measure caption was fixed.
This is available in the latest version of Flexmonster (v2.9.1).
You are welcome to update the component. Here is our updating to the latest version tutorial for guidance.
Please let us know if everything works fine for you.
Kind regards,
Vera
⋅ June 15, 2021
Hello, Vera,
Upgrading to 2.9.1 and adding none back into our list of supported aggregations looks to have fixed the label. Thanks again!
Kind regards,
Henry
