Forum Discussion
Advocate IIZoom Slider Not Working in Online Service
Advocate IIFor me it's completely not clear while this issue is not adressed and there is absolutely no communication at all.
We are a corporation with hundreds of employees, hundreds of charts. This situation is not acceptable and completely emberassing.
I therefore ask you:
- When will this issue be fixed and what can be communicated to our teams?
Anonymous I'm in total agreement with mathiasrh here. My division operates about 200 facilites with an average of 50 trended measures each - that's over 10,000 trend charts that were broken by this change, just for the primary site performance reports. There will be outliers in that many charts over the report period (28 days or ~8,000 points per chart series). Removing markers and drawing connecting lines is not an option for reviewing this sort of data, as each chart is densely populated with data and we want to see the individual markers, not the lines. The control is not a zoom slider if you can't actually use it to zoom in on a desired range of data. Whatever caused this feature to break, you should roll it back to how it was until you find a solution that accomplishes whatever you were trying to do without breaking the zoom slider. This problem is impacting people who support operations at each of these 200 facilities, and for many of these facilities there is more than one impacted report.
It looks like this was resolved in the last week.
Hi!
I don't see it that way. Something has changed indeed.What I see is that the zoom slider now works when the axis limit min/max are "Auto".
When the limit is set to a specific value (fixed or fx) it still doesn't work. The workaround with disabling markers is working in this case as well, so to me the behaviour is still a bug.To make since worse: yesterday I updated Desktop version from August 2024 to January 2025. Now the bug exists in the Desktop version as well.
DataIsGreatIt doesn't look like it to me. The zoom sliders are fine for me in Desktop (my organisation has luckily not gone to January 2025 yet, so I don't yet see the bug there that MZE sees) but do not work when published to the service. I have markers for accessibility (colour-blind users) and set the y-axis min to zero to avoid mis-leading viewers.
