Forum Discussion
How to create source data, e.g. a 'master calendar'?
Is it possible to 'create' a data source using 'query'? I'm trying to create a 'master calendar' that simply needs to contain one column with dates going back, say 3 months, and forward, say 6 months. The idea is to use this to make consistent charts against complete timelines and not only for the dates that appear in my data source. (Or alternatively, is there a way to 'fill' any gaps in data from source?)
amien is your fact table in SQL as well? Or does it come from an independent source?
Just taking a quick look at this again, if everything is in SQL, you can make the code that populates the date dimension tables a procedure and pass in the min/max from the fact table +/- additional months (easy enough to add to the dates you return from the fact table.
Would look something like
Sproc1 - SSCentral script changed to procedure with input parameters for the dates.
Sproc2 -
1) Select start and end date from the fact table
2) Execute the date dimension procedure with the values from the fact table
7 Replies
Wilhelm,
Sounds like you want a date dimension table...
You can create one in multiple ways, this link contains a solution to create a date dimension table in Power Query and references other solutions by other authors as well.
I'm assuming "query" means power query, but if you want a solution in SQL, this builds the table with input parameters. I've used this one alot. SQL Date Dimension
Anonymous, this works well in my Excel files. But what about implementing the same technique in Power BI Desktop? Since upgraded DAX specification has CALENDAR function I think it should be easy. But have no idea how to use it in PBID files neither with "old" Power Query nor newly CALENDAR function. Could someone drop a line about?
You could create a calender table by itself in Excel and just import that as a seperate table into your PBID model. Then create the relationships to your fact tables in PBID.
As for dynamically building it, I don't have a pre-built solution that I've tested out in PBI.
