Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Data Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more

Reply
ArchStanton
Power Participant
Power Participant

Advice about excluding old data

Hi,

My data model is connect to a Live Dynamics CRM system, my report refreshes daily (overnight) and everything is working well.
However, I have a lot of old data from 2018 & 2019 that is not used and I wish to exclude it from my main fact table.

 

What is the best way to do this?

 

My guess is to apply a filter on the Created On date in Power Query that excludes all transactions before 1st Apr 2020. The data that was migrated onto our system is of very poor quality therefore any reporting is based on 2020 onwards where data quality is much better.

 

I just want to check if that is the best way?

I have a lot of existing data transformation steps so should I'm thinking of adding the filter step early on?
The data model is very complicated and the fact table current has ~60,000 rows and 48 columns, removing these 2 yrs will reduce ~4000 rows of rubbish.


1 ACCEPTED SOLUTION
cengizhanarslan
Super User
Super User

If you are sure the business will never report on that migrated 2018–2019 data, then filtering it out in Power Query is the right approach. First, add the filter as early as possible in the query steps, ideally right after the source and type-setting steps. That gives Power BI the best chance to fold the filter back to Dynamics/Dataverse, so fewer rows are pulled before the later transformations run.

_________________________________________________________
If this helped, ✓ Mark as Solution | Kudos appreciated
Connect on LinkedIn | Follow on Medium
AI-assisted tools are used solely for wording support. All conclusions are independently reviewed.

View solution in original post

2 REPLIES 2
cengizhanarslan
Super User
Super User

If you are sure the business will never report on that migrated 2018–2019 data, then filtering it out in Power Query is the right approach. First, add the filter as early as possible in the query steps, ideally right after the source and type-setting steps. That gives Power BI the best chance to fold the filter back to Dynamics/Dataverse, so fewer rows are pulled before the later transformations run.

_________________________________________________________
If this helped, ✓ Mark as Solution | Kudos appreciated
Connect on LinkedIn | Follow on Medium
AI-assisted tools are used solely for wording support. All conclusions are independently reviewed.

Noted, thanks!

Helpful resources

Announcements
Fabric Data Days is here Carousel

Fabric Data Days 2026

Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.

May Power BI Update Carousel

Power BI Monthly Update - May 2026

Check out the May 2026 Power BI update to learn about new features.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.