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,
In few of our reports we have used select * to pull all the columns from the views and as you can imagine its not gone too well with the client.
Is there a way I can easily identify the columns that are actually used in the PBI report, and then only import those from the database.
(I am aware of the tool 'measure killer' which is a great tool, but unfortunetly that only removes the columns AFTER they are imported in the report)
Also note that there are instances we are using a shared dataset and also single dataset single reports.
Thanks!
Solved! Go to Solution.
There is no exact process behind this. The moment you remove a column a business user will call you and ask where that column went.
Your tables should be long and narrow. If they are then you should be able to load all (or most) columns to be prepared for changes in business requirements.
@mandar you can use external tools like our Measure Killer to find what is used in the report or in relationships etc. and what is not.
There is no exact process behind this. The moment you remove a column a business user will call you and ask where that column went.
Your tables should be long and narrow. If they are then you should be able to load all (or most) columns to be prepared for changes in business requirements.
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 |
---|---|
104 | |
95 | |
80 | |
67 | |
62 |
User | Count |
---|---|
147 | |
109 | |
107 | |
85 | |
63 |