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

Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.

Reply
Anonymous
Not applicable

Simple (Date Sliced) Time Distribution w/ Inactive Relation

Hello,

supposedly a very simple problem.

 

"Table1":

fgaertne103119_2-1696007690434.png

...

 

"TimeTable" (full data is 08:00:00 - 16:30:00):

fgaertne103119_1-1696007369380.png

...

 

"DateTable" (2020-07-01 - Today):

fgaertne103119_3-1696007938054.png

....

 

Relationships:

fgaertne103119_4-1696008318782.png

I have a Date Slicer (DateTable[Date]) on my report page and have a visualization for my [LastUpdateTime] (with x-axis [Time_only] & y-axis Measure1 = CALCULATE(COUNTROWS('Table1'), GROUPBY('Table1','Table1'[LastUpdateTime])) )

fgaertne103119_5-1696008378341.png

So far so good, result is as expected (sum of the row count per 1min time window for the date range defined by the Date Slicer).

 

NOW, I would like to have the same visualization on my report page but for [IssueTime].

For this I've tried using the following measure:

Measure2 = CALCULATE(COUNTROWS('Table1'), USERELATIONSHIP(DayTable[Time_only],'Table1'[IssueTime]), GROUPBY('Table1','Table1'[IssueTime]))

 

BUT result is not as expected (not showing any counts or only very few when extending the date range via Date Slicer significantly).

 

What am i missing and how can i solve this problem?

Thanks!

 

 

1 ACCEPTED SOLUTION
Anonymous
Not applicable

I found the solution, the USERELATIONSHIP function has to be wrapped in another CALCULATE like this Measure2 = CALCULATE(CALCULATE(...)), USERELATIONSHIP(..))). Weird because it also clearly had an effect when using it inside a single CALCULATE with the other functions. My lack of DAX knowledge prevents me to properly understand whats happening but fortunately it works now.

View solution in original post

3 REPLIES 3
Anonymous
Not applicable

I found the solution, the USERELATIONSHIP function has to be wrapped in another CALCULATE like this Measure2 = CALCULATE(CALCULATE(...)), USERELATIONSHIP(..))). Weird because it also clearly had an effect when using it inside a single CALCULATE with the other functions. My lack of DAX knowledge prevents me to properly understand whats happening but fortunately it works now.

123abc
Community Champion
Community Champion

..

Anonymous
Not applicable

Sounds like a reply from ChatGPT and looks rather useless to me

Helpful resources

Announcements
LearnSurvey

Fabric certifications survey

Certification feedback opportunity for the community.

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.