Centralized and updated data is a of a strong help!

Thank you, glad to hear that! Hope you found some useful stuff to implement in future projects!

Merci :)

Thanks! When we create the bookmark we select only certain elements, such as the "Dark/light" slicer + toggle images AND update the bookmark to apply only to selected items (check minute 11:00). In this way, the bookmark will only consider those elements and not other that may be changed by the user. Hope it's clear!

Hello, sorry for the delay in my response. I tried to reproduce the steps by publishing the report to service, but not getting the same problem. I suppose there is an issue with the bookmark and/or the 3 elements we are hiding/showing. Have you figured it out or not yet? If not, maybe you could sent me the file (with no data other that the theme of course) so I can check :)

Hello! This is ensured by using the slicer: Dark/light (which is actually hidden). When we "record" the bookmark, we choose the respective value within the slicer. The slicer is then hidden, but its value will be "remembered" by the bookmark. Hope this is clear!

Strange, when you test, are you in Power BI service? Otherwise in Power BI desktop that won't work

Tava pensando o mesmo

I am using measures in order to find the right hex code value corresponding to my text or my background, when selecting a theme. If I take, for example, the background color, I need to identify the hex code corresponding to that. To do so, I am using a calculate function, that will allow me to add a filter to it, and thus find the right value. The filter is Themes[Type]="Background" applied to a calculation that "selects" the value of our color : Selected background = CALCULATE(SELECTEDVALUE(Themes[Color]), Themes[Type]="Background"). This will get our color code, filtered by the type = Background. We apply the same logic to all our measures.

@@captainplatform you are a great teacher of Bi thanks for explaining.

That could be as well a solution. The issue is, if one day you modify the layout, add or change visuals on one of the pages, you'll need to copy/paste / do the same in the other one. With this solution, once you implement that for visuals, you can reuse it. Even if you change a legend, a title, or add an element, it keeps the dynamic formatting and so avoids you to have additional work. But of course, if you want a simple & quick way of doing it, you can create 2 pages and then navigate through them by using a button.

By doing that, you might introduce performance issues; also, if there are other slicers on the page and user has made some selection, unless you sync with the "duplicate" page, the content will be different from one page to the other, confusing user. Great video @Captain Platform!

Thanks for watching and for the feed-back! I though of having something generic that could be easily updated in time and used for many cases. For example, if one day we need to add a new "category", like a specific color for a specific element, we'll have to add that as a row, and not as a column as that implies updating the schema. But I see your point, and indeed if we make it the way you suggest, we don't need to create a measure as we can use directly the value. It's easier to manage it in this way if we don't have a complex theme. On the other hand, if we have too many elements, that could become difficult to manage. It's good to have several solutions for same problem!

Thank you and thanks for advice ! all of those are on the list !

Please make full video on Power BI User Interface

Thanks for watching! More videos on UX and UI will come soon😊

Thanks for watching and the suggestion! Will try to improve that the next time!

I can hear her just perfectly👌👌