Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
It is an issue with newly created formatting for New Card in SU03 / March release. Existing formatting and rules should still apply correctly in the web, and using Feb is a valid workaround. We have fixed this for April Desktop, and are working on a QFE into March Desktop as well (no ETA yet).
To clarify, are you seeing the Warning icon show up in the Visual Header, with text "Style preset not found"?
This is likely due to double-wildcard stylePreset value in your theme file, like:
"*" {
"*" {
"stylePreset" {[
"name": "Flashy Rows"
This used to only apply for Table and Matrix, which shared the same stylePreset options, but now we will try to apply this to all visuals. Since many visuals do not have a stylePreset defined, it will fail to find one and warn you about this. stylePresets for all visuals was just released last week. We will consider only showing this warning in Edit mode, it is not that useful for read-only users.
To fix this, use visualType names specifically for default stylePresets and re-upload your theme.
Note: the latest theme schema update has made validation a bit more strict, so you may need to fix other errors before you can upload themes you have used in the past.
A second issue related to conditional formatting rules for New Slicer (Preview) with May Desktop has been identified, we plan to QFE Desktop within a few days so you can continue to author new format rules for Button and List Slicer in the May release. Existing saved rules are fine. This issue is not related to custom themes. If you save a file with conditional format rules for New Button or List slicer, you may encounter a silent upgrader error, which will cause the formatting to be lost the next time you open the file. The Desktop QFE will fix this for May soon, but Edit/Save in the web will take longer to be patched.
The fix is rolling out, the issue did not impact all regions. We hope to have this completed by the end of tomorrow (April 9th).
The fix is rolling out, the issue did not impact all regions. We hope to have this completed by the end of tomorrow (April 9th).
This should be fixed by now, can you confirm?