Forum Discussion
Help, Please, with DAX Date Processing
- 6 years ago
Hi Anonymous ,
I'm glad to cooperate you to solve the problem. If the answer is helpful, can you please accept it as a solution? Then we are able to close the thread. And more people who have the same request will benefit here.
Best Regards,
Xue Ding
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi Anonymous ,
I found that the "Subset of FactInternetSales21" table is from "FactInternetSales21" table. And there is about 6w rows in it. The two tables take up lots of memory. And the calculation about "Subset" table causes the report slowly. If you don't need "FactInternetSales21" table, I think you could remove it and create the "Subset of FactInternetSales21" table in Query Editor directly. If you still need it, you could remove some columns.Otherwise, you could try to connect the data source with DirectQuery mode.
The ways can solve the problem about memory. However the report still runs slowly, the measure takes too long time (about several hours) to respond so that I can't get a result. You could reference the blogs that my first answer mentioned to optimize it.
Hope the answer will help you a little. I have tried my best.
Best Regards,
Xue Ding
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly. Kudos are nice too.
Thank you so much for all your help, Xue Ding!!
- v-xuding-msft6 years agoCommunity Support
Hi Anonymous ,
I'm glad to cooperate you to solve the problem. If the answer is helpful, can you please accept it as a solution? Then we are able to close the thread. And more people who have the same request will benefit here.
Best Regards,
Xue Ding
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- Anonymous6 years agoNot applicable
My sincere apologies for the delay, Xue Ding!!
After drastically cutting the "Subset of FactInternetSales21" file, to the 1388 records with the lowest CustomerKeys, it now completes and, while I still have some issues to work on, I think those are ones I can handle. My main error was in grossly underestimating PBI's use of memory.
Again, my appreciation for your help!!
- v-xuding-msft6 years agoCommunity Support
Hi Mike ,
I'm very proud for helping you solve it.😊 If you have any problems, please feel free to ask us in the Power BI Community forums.
Best Regards,
Xue Ding