DynamicsCon 2025 - Chicago

Image
I am honored to be presenting at DynamicsCon 2025 in Chicago - May 13 - 16.  https://dynamicscon.com/ I have two sessions: On Wednesday, May 14th at 3:45pm - I am co-presenting with Kent Nielsen.  Our topic is Canvas vs. Model-Driven Power Apps. You can find our slides here:  On Thursday, May 15th at 9:45am - I am presenting one of my most popular sessions - Getting started with Power Automate for D365 F&SCM.  Even if you have seen this session before, there is some new info on environment variables, building solutions and storing approval information in D365. You can find my slides here : 

USERELATIONSHIP in DAX


A common problem many users face it the fact that there are multiple date fields in their tables, and when they want to use a date dimension, Power BI only allows for on active relationship between the two tables.

For example, I have a dimension table from my leasing software that included information on each lease including the commencement date of the lease and the expiration date of the lease.  In Power BI when I use a separate date dimension (which I always recommend for many different reasons), I can only link the dimension table to date table with one active relationship.   See screen shot below.




Since most of my visualizations will be based on the Commencement Date, I will make that the active relationship.  However, I would like to create a visualization showing my leases by expiration date.  In order to do this, I have a couple options.

1.       I could create a second date dimension table in my model.  This is fairly simple.  I would just copy the first dimension and give it a new name (Expiration Date).  I would relate the Lease Details table to the Expiration Date table using the expiration date.  The drawback to this is if you are using date slicers on the report, you would need two different date slicers since they are different tables.  This can also quickly get out of control if there are numerous dates.

2.       I could use the DAX function USERELATIONSHIP.

Userelationship([columnName1],[columnName2])

The function returns no value; the function only enables the indicated relationship for the duration of the calculation.

By using this function I can create a new measure to count my leases based on their expiration date.

Expiring Leases = CALCULATE(DISTINCTCOUNT('Lease Details'[Lease]),USERELATIONSHIP('Lease Details'[ExpirationDate],'Date'[Date]))

Once this measure is in place, I can create my two different visualization using the same date dimension.







Comments

Popular posts from this blog

RPA with Dynamics 365 Finance & Supply Chain

Copilot Dynamics 365 Finance & Supply

Using Full Page Apps in Dynamics 365 Finance