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.
Solved! Go to Solution.
Hi there,
My main suggestion would be not to work with tables containing 160 Columns.
Try modelling your data by using the star Scheme.
This will optimize your report by ALOT for sure.
for example:
You could create a "DIM_DATA" tables with multiple data filtering columns.
The link below is one of the many possible solutions.
https://www.mssqltips.com/sqlservertip/4857/creating-a-date-dimension-table-in-power-bi/
Also creating calculated Columns will slow down your data model quite fast. Try using Calculated measures instead.
check out the "Quick measures" for the ones you suggested.
I hope this wwas any help.
Robbe
Hi,
The correct direction pointed out by his answer, if you still have problem when design, please inform me in details.
By the way, you could refer to Calculating MTD, QTD, YTD, Running and Cumulative Total in Power BI FOR DETAILS.
Best Regards,
Zoe Zhi
Hi there,
My main suggestion would be not to work with tables containing 160 Columns.
Try modelling your data by using the star Scheme.
This will optimize your report by ALOT for sure.
for example:
You could create a "DIM_DATA" tables with multiple data filtering columns.
The link below is one of the many possible solutions.
https://www.mssqltips.com/sqlservertip/4857/creating-a-date-dimension-table-in-power-bi/
Also creating calculated Columns will slow down your data model quite fast. Try using Calculated measures instead.
check out the "Quick measures" for the ones you suggested.
I hope this wwas any help.
Robbe
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 |