Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by watching the DP-600 session on-demand now through April 28th.
Learn moreJoin the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. Register now
Hello,
Let me put you on context first:
1. There are two tables in direct query connection mode
2. I have one fact Table which i had to split in two, the criteria to split both is the date in order to obtain one table with the last four month data, and the other table i want the exact opposite, this means to store all dates which are not in the last 4 months & the current month. The first table wasn`t a problem at filtering i just filtered to keep the last 4 months & the current month dates, but the other one i cannot find how to. I tried this on the steps panel:
= Table.SelectRows(#"Columnas quitadas", each [DateColumn] <> Date.IsInPreviousNMonths([DateColumn],4)). But with this filtering the table just keep loading, and never ends.
Please it would be very helpful some hand here, Thanks!!
Hi @Samuel_sousa ,
Two things:
1) You try a filter condition something like this:
[DateColumn] <= Date.AddMonths([DateColumn], -4)
2) Why have you split the table in the first place? In a Direct Query model, nothing is loaded to the model, so it's not a space- or time-saver. You can make these timebound distinctions in the data with measures for much greater performance.
Pete
Proud to be a Datanaut!
Hello Pete,
I split that table because its too large to be treated, so i need a table with "hot" data which is data with the last 4 months, and "cold" data, which is the data prior to those last 4 months.
I`ve tried the formula you`ve writen, unfortunaly it dindt work:
Samuel.
I'm not sure what you mean by "too large to be treated". You're using Direct Query so no actual data is being loaded to the model. Any transformations you make will be folded back to the source, so there should be no issues with size whatsoever. For the record, I don't think you should be trying to split your table like this at all when using a Direct Qury model. However:
...regarding the failed filter: when you say it's not working, what do you mean? Is it not giving you the required output, or are you getting an error message?
Pete
Proud to be a Datanaut!
Check out the April 2026 Power BI update to learn about new features.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |
| User | Count |
|---|---|
| 8 | |
| 6 | |
| 5 | |
| 5 | |
| 4 |