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.
Is it better to create a view in the database and have Power BI connect to that view, or would it be more viable to create parameters to filter data/queries?
Say I have a table which is fairly massive but I want to report on it per 'region' (based on a dimension in table). Currently, I create a view in the database and then connect Power BI and refresh the charts and it seems to work well. As more 'regions' become interested in having their own dashboard, I have to create and manage additional views though. It would be nice if the end-user could filter for their own region and have the data refresh.
Solved! Go to Solution.
It's better to import views instead of tables into Power BI to avoid strong dependency between the physical data model and the report. Please see: Data Import Best Practices in Power BI.
And I don't suggest use Query Parameter since it can't be used on Power BI Service.
Regards,
Simon Hou
It's better to import views instead of tables into Power BI to avoid strong dependency between the physical data model and the report. Please see: Data Import Best Practices in Power BI.
And I don't suggest use Query Parameter since it can't be used on Power BI Service.
Regards,
Simon Hou
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 |
---|---|
109 | |
99 | |
77 | |
66 | |
54 |
User | Count |
---|---|
144 | |
104 | |
102 | |
87 | |
64 |