Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I have a semantic model with a lot of hidden fields. These fields are used for things such as keys or other measures. I've recently noticed that these fields show up when someone takes a visualization and goes to add conditional formatting. WHen they go to select fields to utilize for the calculation they can select the hidden fields as well.
Is there a way I can make sure my hidden fields are hidden from everything? Including conditional formatting selections?
Solved! Go to Solution.
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
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.
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.
I wouldn't say it was "resolved" as the answers are not to my liking... but they are what they are.
Hi,
you can hide the entire table in your semantic model using Tabular Editior (set as private).
Unfortunatelly it cant be done just for particular fields.
Hi @Don-Bot
Unfortunately, there's currently no way to fully hide fields from everything, including conditional formatting selections.
Marking fields as "hidden" works for the report view and hides them from end users in the Fields pane, especially when connecting to a published dataset (e.g., in the Service or via DirectQuery/Live Connection). However, the fields are still technically part of the model and remain accessible for things like measures and conditional formatting options.
So even if a field is hidden, it can still appear in the conditional formatting field selection dialog.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
71 | |
70 | |
43 | |
31 | |
26 |
User | Count |
---|---|
89 | |
49 | |
44 | |
38 | |
37 |