Forum Discussion

vbourbeau's avatar
vbourbeau
Resolver II
5 years ago
Solved

date dimension best practice

Hi,   Simple question today. Do you think it is a best practice to create date dimension in a dataflow in the service?  My concern is because I have many reports and don't want to always copy the ...
Need Help
  • Greg_Deckler's avatar
    Greg_Deckler
    5 years ago

    vbourbeau Yes, that would be a good solution as everybody could use it and it would benefit from compression if applicable. Things like Year columns, Month names and month numbers would compress. Things like date or unique keys would not obviously.

Kave's avatar
Kave
Regular Visitor
4 years ago

Hi, Great to see your question/case. It's exactly the one that I have in my mind for my project.
As you mentioned, I created a DataFlow for DateDimention to be able to use it again and again in many reports in PBI Service. It seems to be the best solution for our case. By doing so, there is no need to update/change all the internal Date tables, but the original one. Very practical solution.
Just one issue, at the time of writing this comment!
It's not possible to add a column to the main Date table. The reports just get the updating / changing the current column, and no idea about the added columns. I have to download the report from Cloud into the desktop, then refreshing, and then get the added column. At last, I should upload it again into the Cloud.
Please let me know if I have any mistakes in the process.

Thanks...