Fabric is Generally Available. Browse Fabric Presentations. Work towards your Fabric certification with the Cloud Skills Challenge.
Account table |
Account Number |
Client id |
date opened |
Issue table |
Account Number |
Date received |
Solved! Go to Solution.
I made changes to the issue table , added client id to the issue table and then joined issue table to client table in the dataset and it works fine now.
I made changes to the issue table , added client id to the issue table and then joined issue table to client table in the dataset and it works fine now.
That's a pretty small dataset. I would have written that measure like this, but I would not have expected your version to have memory issues. Do you have another path between these two tables in your model (i.e., ambiguity)? Any bi-directional relationships? I'm assuming you the Accounts table is the 1 side, and that you are using the Client ID column from that table in your visual.
Number of Acc Opened after tag on =
VAR _date_rec =
MIN ( 'Issue'[Date Received] )
RETURN
CALCULATE (
COUNTROWS ( account[Account Number] ),
account[Date Opened] > _date_rec
)
Pat
I made changes to the issue table , added client id to the issue table and then joined issue table to client table in the dataset and it works fine now.
@_Regina , try with this small chnage
Number of Acc Opened after tag on =
var _date_rec= CALCULATE(min('Issue'[Date Received]))
return
CALCULATE(DISTINCTCOUNT(account[Account Number]),filter(account, account[Date Opened]>_date_rec) )
I made changes to the issue table , added client id to the issue table and then joined issue table to client table in the dataset and it works fine now.
Check out the November 2023 Power BI update to learn about new features.
Read the latest Fabric Community announcements, including updates on Power BI, Synapse, Data Factory and Data Activator.