Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi,
Is there a way, whether free or fee-based, to identify every field used in a Power BI report, and how?
One way would be to view the Source of each Power Query query to understand each field in use, and this would be the most basic method, but through this way we wouldn't understand how each field was used - i.e. was the source field used in the following scenarios:
1) Brought into Power Query but never used (maybe deleted within Power Query, or left in a non-enabled query).
2) Was used to filter data in Power Query but didn't get to be 'Close & Apply' so to move over to the Power BI side.
3) It is in the Power BI side but used just a field (i.e. not used in a measure or filter).
4) It is used in a DAX measure.
5) It is used in a filter (visual filter or report pane filter).
The reason why I ask is, if a change to the source system is made (i.e. a field/column name is changed, or a field value changes which may affect filtering used on a field value) then this can/will break the report.
Rather than having the end-user ask me "We are about to change a source system's field/column name or field's value - will this break any reports?" then I have to scope all reports' content to answer the question, it would be nice to record up-front all the fields used and how they are used in the report.
Does anyone know how this can be achieved?
Is this a common process for fellow Power BIers and how do you cater for this scenario currently?
Thanks.
Solved! Go to Solution.
@D_PBI ,
Unfortunately power query doesn't have such feature like previously scanning all the column headers in the data source before importing. The power query code will be transformed into sql statement in mashup engine like pattern:
SELECT column1, column2, ...
FROM table_name;
So if the column name is incorrect, error occurs. To solve this, I'm afraid you need to modify the headers in advanced editor manually. You can also submit your idea here.
Community Support Team _ Jimmy Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
@D_PBI ,
Unfortunately power query doesn't have such feature like previously scanning all the column headers in the data source before importing. The power query code will be transformed into sql statement in mashup engine like pattern:
SELECT column1, column2, ...
FROM table_name;
So if the column name is incorrect, error occurs. To solve this, I'm afraid you need to modify the headers in advanced editor manually. You can also submit your idea here.
Community Support Team _ Jimmy Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Refer, if this can help
https://community.powerbi.com/t5/Desktop/power-bi-metadata/td-p/335671
@D_PBI , do you need more information
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
114 | |
99 | |
82 | |
70 | |
60 |
User | Count |
---|---|
149 | |
114 | |
107 | |
89 | |
67 |