Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hi Team,
In Power BI, calculated columns are easy to identify because they have a distinct icon. However, when I create conditional columns, I don’t see a clear way to distinguish them. Is there any method to identify which columns were created as conditional columns? I sometimes lose track of the ones I’ve added.
Solved! Go to Solution.
Hi @dayawan I'm assuming you're referring to a coniditional column created in the query editor. In Power BI, a custom column created in the Power Query editor exists only at the query stage and is treated like any other column once the table is loaded into the data model. The model has no built-in way to identify it as custom, so it cannot distinguish between columns from the original source and those added or transformed in Power Query, meaning all columns are effectively equal in the model and any “custom” identity is lost unless manually documented or flagged (adding an indentifier in the column name).
Hi @dayawan,
Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.
Best regards,
Prasanna Kumar
Hi @dayawan,
Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to @grazitti_sapna , @danextian and @MasonMA for prompt and helpful responses.
Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.
Best regards,
Prasanna Kumar
No, for others' files, you would have to inspect each query step in Applied Steps to find out which columns were added as conditional columns in case the step names were renamed. For you own queries, i'd suggest renaming those conditional Columns with certain flags so that you can identify them in a quick way later.
Hi @dayawan I'm assuming you're referring to a coniditional column created in the query editor. In Power BI, a custom column created in the Power Query editor exists only at the query stage and is treated like any other column once the table is loaded into the data model. The model has no built-in way to identify it as custom, so it cannot distinguish between columns from the original source and those added or transformed in Power Query, meaning all columns are effectively equal in the model and any “custom” identity is lost unless manually documented or flagged (adding an indentifier in the column name).
Hi @dayawan,
There is no easy way to identify the conditional column created in Power Query as Power BI doesn't assign a logo to it, But you can rename the applied step in Power Query as added conditional [column name], or you can prefix column something like Cndsnl_[column name], so that you can easily identify that this is a conditional column.
🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 50 | |
| 44 | |
| 42 | |
| 19 | |
| 19 |
| User | Count |
|---|---|
| 70 | |
| 68 | |
| 33 | |
| 32 | |
| 32 |