You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Slicer 'Styles' were migrated from being in the visual header drop-down menu to now being in the 'Style' general formatting menu.
The JSON schema still only supports orientation enum options of 0 and 1 for vertical list vs horizontal tile orientations here and does not support the additional 'Style' options that now include things like making the slicer a drop-down list by default or a 'between', 'relative date', etc.
The {*} > {*} > {mode} in the json schema appears to list all these new style options but when I set define this way, it doesn't appear to be applying in-app.
The {*} > {general} > {orientation} enums of 0 and 1 do still work to switch between VerticalList and HorizontalList, but don't accept any additional enum values that might represent Dropdown mode as far as I can tell.
Is there another way to set the slicer orientation / mode / style via json?
The text was updated successfully, but these errors were encountered:
Slicer 'Styles' were migrated from being in the visual header drop-down menu to now being in the 'Style' general formatting menu.
The JSON schema still only supports orientation enum options of 0 and 1 for vertical list vs horizontal tile orientations here and does not support the additional 'Style' options that now include things like making the slicer a drop-down list by default or a 'between', 'relative date', etc.
The {*} > {*} > {mode} in the json schema appears to list all these new style options but when I set define this way, it doesn't appear to be applying in-app.
The {*} > {general} > {orientation} enums of 0 and 1 do still work to switch between VerticalList and HorizontalList, but don't accept any additional enum values that might represent Dropdown mode as far as I can tell.
Is there another way to set the slicer orientation / mode / style via json?
The text was updated successfully, but these errors were encountered: