Forum Discussion
Direct query, not able to make changes
You can safely add a month number column to either your fact table or your calendar table (I'd recommend the calendar table) in Power Query using just Date.Month([Date]). This will fold to the server and is, therefore, fine for use in a Direct Query model.
Once you have that column, you can select your month name column in the Modelling tab, and use the 'Sort by column' dropdown under Advanced settings to assign it to sort by Month number:
Pete
Hi Susan12344 ,
Firstly, Direct Query is generally used in the following two scenarios:
1) You need up-to-the-second data
...and/or...
2) Your dataset is billions of rows and too big to reasonably be imported
If your report/dataset does not meet either of these criteria, then I would recommend switching to import mode.
Secondly, I would strongly recommend that you create a separate date/calendar table as a matter of course. It's generally-accepted best practice, and gives you full access to Power BI's OTB time intelligence functions. It also makes it really easy to sort month names in chronological order.
Pete
Thank you! The dataset is indeed way to big to be imported. I already have a date/calender linked to many visuals, but like I mentioned- it's not really doing its job well.
My question was more if I can avoid making a whole new table and linking the new stuff to all the visuals or if i have no other choice.You can safely add a month number column to either your fact table or your calendar table (I'd recommend the calendar table) in Power Query using just Date.Month([Date]). This will fold to the server and is, therefore, fine for use in a Direct Query model.
Once you have that column, you can select your month name column in the Modelling tab, and use the 'Sort by column' dropdown under Advanced settings to assign it to sort by Month number:
Pete
