Forum Discussion
Hierarchy Slicer - Unexpected Error
- 9 years ago
All,
I have submitted a new version for approval that fixes the 'unexpected error' and after approval it will be available asap.
Sorry for the inconvenience.
Thanks, JP
I have the error too. I get the symbols marked with yellow as an "extra" on Chrome only. On Desktop and Explorer works fine.
Thanks
Yes it seems to be related to Chrome only, but fix is being reviewed.
- Anonymous8 years agoNot applicable
I am seeing similar in IE11 too.
- Anonymous8 years agoNot applicable
I am seeing similar behavior in IE11 too.
- Anonymous8 years agoNot applicable
The regular silicers have an "eraser" on them. I thought this one did too, but it doesn't seem to be there now. Any chance it would added?
- lukomskicl8 years agoFrequent Visitor
Any idea on when the Hierarchy Slicer will be fixed in Desktop? It is not working properly. You can't see all the levels and you can't clear the selections. Please help provide a fix.
- jppp8 years ago
Continued Contributor
There is a new version comming that fixes the following issues:
- Header issue where the three icons are showing way to big in Chrome
- Single select of top level that is not working
- Collapse/Expand all icons are not working
Currently this version is still in review before it can be released to everyone.
Thanks, Jan Pieter
- Anonymous8 years agoNot applicable
jppp wrote:There is a new version comming that fixes the following issues:
- Header issue where the three icons are showing way to big in Chrome
- Single select of top level that is not working
- Collapse/Expand all icons are not working
Currently this version is still in review before it can be released to everyone.
Thanks, Jan Pieter
----------------------------------------------------------------------------------------------------
Hi Jan,
i see that on all hierarchy slicers i am not able to go to the lower levels and is happening only in Chrome.We have many reports and dashboards that are using this control and we are facing this issue.
Also this issue is affecting only some users and for some users it is working fine.
Did your recent fix this issue?thanks in advance
Regards,
CLR