![]() ![]() Yesterday I was amending this structure to add budget periods to one tab in the visual forgetting that the slicers were synced. I think the only way I could fix it was to recreate the slicers. These dates were retained and essentially blanked all the visuals which had measures that used the selected values from the slicers. ![]() It works really well, however, when I was switching the queries from one project to the other I left the slicers on dates that did not exist in the first project. I have a Start slicer and a Finish slicer that are in synch with each other so that the dates cannot inadvertently be crossed (by selecting a finish date that is earlier then the start date). The query that creates the table takes all the month records from the date table and merges them with themselves. In the 1st instance I have a report that I created that uses a disconnected table to get the start and end months from my date calendar. I ran into this issue a couple of weeks ago and also yesterday and can confirm the authors impressions. As always, I’m interested in your thoughts and comments. That said I can’t help wondering if there are situations where this behaviour could be useful, for example in scenarios where you want to show an initial selection that displays no data but which can’t subsequently be reselected by an end user. In any case, in the real world I always try to avoid situations where the values in a slicer might disappear: if you have a dimensional model and are building slicers from dimension tables rather than fact tables, you should find that values are rarely removed from dimension tables, if ever. In my opinion this behaviour makes sense and shouldn’t be changed. Once again, if you select something else in the slicer, the –1 value will disappear. …and then select the value –1 in the new slicer, you’ll see it results in the value –1 appearing as selected in the original slicer even though that value does not appear in the underlying column: If you create a slicer from this table, use Sync Slicers to synchronise it with the existing slicer on the report shown above: For example, say you have a second table created as a DAX calculated table with the following expression: Something similar may occur when using the Sync Slicers functionality to synchronise two slicers with different source columns that contain different values (as described here). As soon as another value in the slicer is selected (in this case 83), the value 78 disappears from the slicer.Even though 78 appears and is selected, the measure returns “Nothing Selected” because the DAX SelectedValue() function has detected that no single value has been selected.However, because 78 was selected before refresh took place, it still appears – and is still selected in – the slicer as an extra value meaning there are now six items visible in the slicer.After the refresh has taken place the number 78 no longer appears in the underlying table, which contains five rows still.Now what happens when you refresh the dataset and the table contains a different set of numbers? Here’s what: In the screenshot above you can see I have selected the value 78 in the slicer and the measure – as you would expect – displays that value. SELECTEDVALUE(MyNumbers, "Nothing Selected")
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |