Hello,
We had the following observation for the Conditional Formatting popup. If we define a conditional format for a measure that is on the pivot table and then deactivate it from the fields popup, then in the Conditional Formatting popup, there is still an entry for that field, but the "Value" box is blank. The same thing happens if we predefined a condition for a measure within the Report object that is not listed in the Measures object. Is this the intended behavior? If so, is there a way we can show the measure's name in the Conditional Formatting popup regardless of whether it is active or not? We've prepared a video and jsFiddle for convenience
Please let us know if you have any troubles opening the video or jsFiddle!
Kind regards,
Henry
Hello, Henry,
Thank you for reaching out to us and for explaining the case in such detail.
We would like to confirm that this is not the expected behavior.
Our team will provide an update so that the measure's name is displayed in the Conditional Formatting popup regardless of whether it is active or not.
Also, we noticed that in some cases the measures dropdown position is shifted. Our team will also provide a fix so that the dropdown is rendered at the correct position.
These updates will be available in the minor release version of Flexmonster with the ETA 12th of April.
Please let us know if this would work fine for you.
Looking forward to your reply.
Kind regards,
Vera
Hello, Vera,
Yup, that will work for us, thanks again!
Kind regards,
Henry
Hello, Henry,
We would like to kindly explain that the updates will be available a bit later, ETA April 19th.
Please let us know if this would work fine for you.
Kind regards,
Vera
Hello, Vera,
Not a problem, that will work for us!
Kind regards,
Henry
Hello, Henry,
We are happy to announce that the issue with the blank measure’s name in the conditional formatting pop-up was fixed.
Also, our team fixed the issue with the dropdown position being shifted inside the conditional formatting pop-up.
This is available in the latest version of Flexmonster.
You are welcome to update the component. Here is our updating to the latest version guide for assistance.
Please let us know if the update works fine for you.
Looking forward to your feedback.
Kind regards,
Vera
Hello, Vera,
The update looks to have resolved the blank measure's name in the conditional formatting pop-up. However, we noticed some odd behavior when it came to resizing our browser window. We are not not sure if it is related to this issue or not because the issue describe there has been fixed with this update.
The behavior we noticed is that when we resize our browser, the width and/or height of the pivot table appears to be stuck at the initial width/height it is rendered as. For example, if our browser takes up half of the screen, the pivot table will render normally with scrollbars as needed. However, when we maximize our browser, the pivot table does not grow with the browser.
We are unfortunately unable to replicate it with a jsFiddle because we think it only applies to Angular, or at least from our observations. We will try to describe it in detail, please let us know if any clarifications or additional information is needed:
#fm-pivot-view
seems to have its height and width element styles updated as the browser width and height changes. Similarly, the second child of #fm-pivot-view
with the class selectors fm-ui-element fm-ui fm-ui-container fm-grid-view
also has its height and width element styles adjusted in a similar fashion
#fm-pivot-view
remain fixed at its initial width and height as the browser size changes.
Is there perhaps a new configuration within the pivot table that we might have missed as a part of upgrading to 2.8.31?
Kind regards,
Henry
Hello, Henry,
Thank you for your reply.
Our team is happy to hear that the initial issue is fixed.
Regarding the resizing behavior:
With this minor release, we have updated the Angular wrapper to adjust the height better.
The expected behavior for Flexmonster is to take up 500px
in height and 100%
in width. To make Flexmonster adjust its height to fit its parent container, the height
property should be set to 100%
. In Angular, we found an inconsistency that we addressed in this minor release.
However, using the layout in your JSFiddle, we have managed to reproduce the issue on our sample Angular project. Our team will look into this in more detail, and we will share the results with the ETA 5th of May.
Please let us know if this would work fine for you.
Kind regards,
Vera
Hello, Vera,
That will work for us, thanks again!
Kind regards,
Henry
Hello, Henry,
We are happy to inform you that our team provided an update in the 2.8.32 version of Flexmonster for the Angular wrapper. Now the resize behavior should work as before.
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
Hello, Vera,
Upgrading to 2.8.32 looks to have restored the resize behavior. Much thanks to you and the team!
Kind regards,
Henry