When creating field value conditional formatting, Power BI no longer accepts measures that evaluate to strings. This hasn't been the case but apparently changed in an update or with a feature at some point.
BUG BEHAVIOR
For example, let's say I have a measure called Red that contains a string as follows:
Red = "#CF000F"
I then have a formatting measure that references that measure:
SlicerTitle = [Red]
The SlicerTitle measure can now no longer be added to Field Value conditional formatting:
ODD BEHAVIOR
However, visuals that had this measure added successfully in the past still work. Additionally, it starts working if I:
- Change the [SlicerTitle] reference to the [Red] measure to an explicit color string (i.e., SlicerTitle = "#CF000F").
- Add the measure as field value formatting to a visual (PBI accepts this because strings are explicitly written).
- Add the reference to the [Red] measure back in after adding to visual (i.e., change SlicerTitle = "#CF000F" back to SlicerTitle = [Red]).
REALLY hope this gets fixed as it is incredibly frustrating to have to do workarounds.
Comments
- accowize on: Error "[403.12–403.30] The name 'Lakehouse.Content...
- MaAl on: "The import PowerPlatform.Dataflows matches no exp...
-
NikNithiy
on:
URGENT!! Paginated Report not loading on Mozilla F...
- duarte on: Unable to sort months in PowerBI
- adam_hfg on: Matrix Visual doesn't work with Field Parameters ...
-
mattlee
on:
“Add Value” in Textbox Not Visible in Dark Theme
- mattin on: Report Server Permissions Jan/May 2025
-
bhalicki
on:
Bi Crashes on launch with (AS Process PID=XXXXXX H...
- stanteitelbaum on: authenticator wont trigger after purchase of new p...
-
Stinkys
on:
Fix the Date function in DAX