Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Hello everyone, thanks in advance for helping. I am kinda new in Power Bi and DAS.
I do have a table with 2 fields, Patient (Identifier of my patients) and Date (Exact day when I assist them). I do want to obtain a new 2 columns.
The first one (Unique) should let me know if I have seen the patient before (yes) or just 1 time (no).
The second one (Repeated) should let me know how many times I have seen the patient.
I post here an example of 4 patients and who the new calculated fields (columns Unique and repeated) should look like.
Patient | Date | Unique | Repeated |
AR | 01/01/2018 | NO | 1 |
AR | 03/01/2018 | NO | 2 |
AR | 01/03/2017 | NO | 0 |
UN1 | 04/08/2019 | YES | 0 |
UN2 | 07/02/2015 | YES | 0 |
BO | 01/01/2015 | NO | 1 |
BO | 02/02/2016 | NO | 2 |
BO | 08/07/2019 | NO | 3 |
BO | 01/02/2000 | NO | 0 |
Any ideas,
Thanks a lot!
Solved! Go to Solution.
Sure. Unique should be a pretty easy DAX measure:
Unique = IF( CALCULATE( COUNT(Table1[Patient]), ALL(Table1) ) > 1,
"NO",
"YES")
Repeated is slightly harder, but still easy DAX:
Repeated = CALCULATE( COUNT(Table1[Patient]),
FILTER(ALLEXCEPT(Table1, Table1[Patient]), Table1[Date] < SELECTEDVALUE(Table1[Date]) )
)
Hi Angel,
Could it be because you are giving semicolon and not comma after NO?
( screensnot below)
@areymejias regarding repeated, you can try:
Sure. Unique should be a pretty easy DAX measure:
Unique = IF( CALCULATE( COUNT(Table1[Patient]), ALL(Table1) ) > 1,
"NO",
"YES")
Repeated is slightly harder, but still easy DAX:
Repeated = CALCULATE( COUNT(Table1[Patient]),
FILTER(ALLEXCEPT(Table1, Table1[Patient]), Table1[Date] < SELECTEDVALUE(Table1[Date]) )
)
Hello @Cmcmahan , Thanks a lot for your reply!!
But it does not work. If you try it with the table above. It returns an error message: "The syntax for "NO" is an error (DAX(
Yup. This is 100% due to regional settings. You'll have that issue pretty commonly on the board. There's a good mix of us that use commas instead of semicolons and vice versa. Double check any queries you get here for basic structure.
Hi Angel,
Could it be because you are giving semicolon and not comma after NO?
( screensnot below)
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
87 | |
85 | |
82 | |
66 | |
49 |
User | Count |
---|---|
137 | |
111 | |
101 | |
66 | |
65 |