Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
I have a table that includes the following:
Last_Register | No | Version | Status | Account | Last_Trip | EE | Count Emails | Remove | |
11/15/2022 13:42 | person1@gmail.com | 12345678 | 1 | not avail | 12345 | 123 | 2 | FALSE | |
3/9/2023 7:09 | person1@gmail.com | 12345678 | 2 | registered | 23456 | 3/9/2023 11:39 | 123 | 2 | FALSE |
2/11/2023 13:05 | person2@gmail.com | 23456789 | 1 | not avail | 34567 | 2/11/2023 17:45 | 345 | 3 | FALSE |
3/9/2023 7:28 | person2@gmail.com | 23456789 | 1 | registered | 45678 | 3/9/2023 11:59 | 345 | 3 | FALSE |
3/9/2023 7:30 | person2@gmail.com | 34567890 | 2 | registered | 56789 | 345 | 3 | FALSE | |
3/7/2023 16:40 | person3@gmail.com | 45678901 | 1 | pending | 67890 | 3/7/2023 21:16 | 678 | 2 | FALSE |
3/9/2023 7:26 | person3@gmail.com | 45678901 | 1 | registered | 78901 | 678 | 2 | FALSE |
I am trying to create a "Remove" filter to determine whether the record should be removed from the data.
So first I need to identify dup records based on email. Then, based on certain criteria involving No, status and registered date, I need to build logic to determine which record(s) to remove. I created a "Remove" column which is FALSE for now (until I build the logic).
I was able to identify records with duplicate emails by creating the following column:
Last_Register | No | Version | Status | Account | Last_Trip | Employee No | Count Emails | Remove | |
11/15/2022 13:42 | person1@gmail.com | 12345678 | 1 | not avail | 12345 | 123 | 2 | TRUE | |
3/9/2023 7:09 | person1@gmail.com | 12345678 | 2 | registered | 23456 | 3/9/2023 11:39 | 123 | 2 | FALSE |
2/11/2023 13:05 | person2@gmail.com | 23456789 | 1 | not avail | 34567 | 2/11/2023 17:45 | 345 | 3 | TRUE |
3/9/2023 7:28 | person2@gmail.com | 23456789 | 1 | registered | 45678 | 3/9/2023 11:59 | 345 | 3 | TRUE |
3/9/2023 7:30 | person2@gmail.com | 34567890 | 2 | registered | 56789 | 345 | 3 | FALSE | |
3/7/2023 16:40 | person3@gmail.com | 45678901 | 1 | pending | 67890 | 3/7/2023 21:16 | 678 | 2 | TRUE |
3/9/2023 7:26 | person3@gmail.com | 45678901 | 1 | registered | 78901 | 678 | 2 | FALSE |
Solved! Go to Solution.
Thanks to the great efforts by MS engineers to simplify syntax of DAX! Most beginners are SUCCESSFULLY MISLED to think that they could easily master DAX; but it turns out that the intricacy of the most frequently used RANKX() is still way beyond their comprehension! |
DAX is simple, but NOT EASY! |
Thanks to the great efforts by MS engineers to simplify syntax of DAX! Most beginners are SUCCESSFULLY MISLED to think that they could easily master DAX; but it turns out that the intricacy of the most frequently used RANKX() is still way beyond their comprehension! |
DAX is simple, but NOT EASY! |
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
58 | |
56 | |
56 | |
38 | |
29 |
User | Count |
---|---|
75 | |
62 | |
45 | |
40 | |
39 |