Forum Discussion
Field Description not available for columns
Hi all,
I have built a data dictionary for all the reports in our workspace, using "select * from $SYSTEM.TMSCHEMA_COLUMNS" and "select * from $SYSTEM.TMSCHEMA_MEASURES".
The problem I have come across is that while I am able to add a Description for measures as seen below.
I am unable to do the same for columns and calculated columns. The properties pane does not even appear when selecting them.
Should the properties pane be available for columns?
Is there a different way to add a description for columns (such that it is part of the description metadata) within power bi?
If not is there an alternative?
- Anonymous3 years ago
Thanks for the reply Owen. Not super sure what the issue was but any changes in power query seems to resolve it. Such as adding a blank query and removing a parameter. Im guessing it was some kind of state issue that changing something in power query resolves.
2 Replies
- OwenAuger
Super User
Anonymous
That's odd!
Descriptions for columns (whether calculated or not) are editable in Power BI Desktop (when the PBIX contains a dataset).
I haven't been able to replicate the behaviour you're seeing 😞
When any column is selected in the model view, you should see the Properties pane > General section, as shown below.
Also, the Properties pane > Cards section in your screenshots should only be visible when no columns/measures are selected.
Checking a couple of things:
- Is there anything unusual about the PBIX or your version of Power BI Desktop?
- Does your PBIX definitely contain a dataset (rather than being a report live-connected to another dataset)?
(In this case, you should still see Properties pane > General but read-only.)
Could you share a link to a PBIX exhibiting the issue with data or anything sensitive removed?
Site note: You could use a script in Tabular Editor to load the descriptions to the model in bulk.
- AnonymousNot applicable
Thanks for the reply Owen. Not super sure what the issue was but any changes in power query seems to resolve it. Such as adding a blank query and removing a parameter. Im guessing it was some kind of state issue that changing something in power query resolves.