Best practice for models using "between" relationships

[JrBIAnalyst]

What is the best practice for compensating for Power BI's lack of a "between" style relationship?

I'm working with tables in source systems that are intended to be joined based on a value in the fact table falling between two values in the dimension table. As designed, these tables are supposed be related by "Fact_Table JOIN Dimension_Table on Fact_Table.Date between Dimension_Table.Valid_From and Dimension_Table.Valid_To" 

Other than joining these to create one table in Power Query, what is the best practice for creating a relationship like this in the data model? 

[pratyashasamal]

Hi  ,
You can read these links :-
https://blog.enterprisedna.co/data-modelling-in-power-bi-tips-best-practices/

https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-relationships-understand

https://www.powerbitutorial.org/tutorials/how-to-implement-date-tables/

Thanks,
Pratyasha Samal
Has this post solved your problem? Please Accept as Solution so that others can find it quickly and to let the community know your problem has been solved.
If you found this post helpful, please give Kudos C

[JrBIAnalyst]

Thanks, @pratyashasamal. Unfortunately those don't really cover my question. They do a great job covering best practices of data modelling within the kind of relationships that Power BI was designed to accomodate. Unfortunately, Power BI wasn't designed to accomodate these range-based relationships, so this exiosting documentation doesn't address how to immitate that behavior.