Forum Discussion
Hide fields from showing up in conditional formatting selection
- 1 year ago
Hi Don-Bot ,
Thanks for reaching out to the Microsoft fabric community forum.
To Prevent Internal Fields from Showing in Conditional Formatting -
-
Group Helper Fields in a Separate Folder
You can organize all your utility or backend measures into a clearly labeled display folder like "Helper_DoNotUse". While this won't stop those fields from showing up in things like conditional formatting menus, it helps make it clear to report authors that these fields are not meant to be used directly. -
Use Clear Naming Conventions
Naming internal-only fields with a prefix like _InternalKey or _CalcOnlyMeasure is another good practice. It acts as a visual cue for other users to avoid selecting them by mistake. -
Leverage XMLA Endpoint for Governance (Premium/PPU Only)
If you're working in a Premium or PPU workspace, you can connect to your model using Tabular Editor and apply more advanced settings. For example, setting isHidden = true on specific fields can help control visibility at the metadata level. -
Create Perspectives for Report Authors
Also in Tabular Editor (with Premium/PPU), you can build Perspectives—custom views of your data model that only show the fields you want report builders to use. This helps clean up the experience and keeps internal logic or technical fields out of the way. While perspectives don’t completely hide fields in conditional formatting, they’re still very useful for managing what shows up in tools like Excel or when using Analyze in Excel.
If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it
Best Regards,
Sreeteja.
Community Support Team -
Hi Don-Bot ,
Thanks for reaching out to the Microsoft fabric community forum.
To Prevent Internal Fields from Showing in Conditional Formatting -
-
Group Helper Fields in a Separate Folder
You can organize all your utility or backend measures into a clearly labeled display folder like "Helper_DoNotUse". While this won't stop those fields from showing up in things like conditional formatting menus, it helps make it clear to report authors that these fields are not meant to be used directly. -
Use Clear Naming Conventions
Naming internal-only fields with a prefix like _InternalKey or _CalcOnlyMeasure is another good practice. It acts as a visual cue for other users to avoid selecting them by mistake. -
Leverage XMLA Endpoint for Governance (Premium/PPU Only)
If you're working in a Premium or PPU workspace, you can connect to your model using Tabular Editor and apply more advanced settings. For example, setting isHidden = true on specific fields can help control visibility at the metadata level. -
Create Perspectives for Report Authors
Also in Tabular Editor (with Premium/PPU), you can build Perspectives—custom views of your data model that only show the fields you want report builders to use. This helps clean up the experience and keeps internal logic or technical fields out of the way. While perspectives don’t completely hide fields in conditional formatting, they’re still very useful for managing what shows up in tools like Excel or when using Analyze in Excel.
If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it
Best Regards,
Sreeteja.
Community Support Team
- v-sshirivolu1 year agoCommunity Support
Hi Don-Bot ,
Just wanted to check if you had the opportunity to review the suggestion provided?If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it.
- v-sshirivolu1 year agoCommunity Support
Hi Don-Bot ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and Accept it as the solution and give a 'Kudos'. This will be helpful for other community members who have similar problems to solve it faster.
- Don-Bot1 year agoHelper V
I wouldn't say it was "resolved" as the answers are not to my liking... but they are what they are.