Forum Discussion
Power Query vs. Aggregating in Power BI: Issue or bug?
With hundredths of a second apart it will depend on the format used and you may need to convert it to use it the visual correctly. The solution here might help:
Power Query will work a lot better with this without any additional formatting for a visual so i'd recommend using the aggregation there.
If I answered your question, please mark my post as solution, Appreciate your Kudos 👍
Also, if there is a difference and I have to live with it, which one do I go with?
I'd start by comparing the lists to see which ones are missing, i'd imagine that the unique datetime field should make it so that there's no duplicate records?
Once you've identified which are missing you'll be able to either figure out what's causing the issue or at least know which is correct to decide which to go with. I'd guess that Power Query is the accurate one but without seeing the data and what's happening it's a best guess.
If I answered your question, please mark my post as solution, Appreciate your Kudos 👍
These are the first 20 entries. Names are fake and emails redacted, but the "Lookup" column reflects a quick MATCH between what the aggregated table produces in Power Query and what I get when I use the aggregation in the visual (count distinct) and then filter the visual to give me anybody with a logon count of < 5. The only thing I can think of that causes this is that Power BI for some reason cannot discern between hundredths of a second when doing the count. The entries that are missing are people that have logons literally one right after the other, a hundredth of a second apart. Thoughts?
+-------------+--------------+-------------------------+-------+--------+ | First Name | Last Name | Username | Count | Lookup | +-------------+--------------+-------------------------+-------+--------+ | Allen | Flores | [email protected] | 3 | #N/A | | Alyssa | Poole | [email protected] | 1 | 1 | | Bobbi | Karpus | [email protected] | 1 | #N/A | | Brandie | Rucker | [email protected] | 1 | 2 | | Brent | Strachan | [email protected] | 1 | #N/A | | Brian | Olesko | [email protected] | 3 | 4 | | Bruce | Marshall | [email protected] | 3 | 5 | | Bryan | Holt | [email protected] | 1 | #N/A | | Bryan | Stuehrenberg | [email protected] | 2 | #N/A | | Cami | Hunt | [email protected] | 1 | 6 | | Chris | Ginest | [email protected] | 1 | 7 | | Christopher | Tulga | [email protected] | 3 | 8 | | Courtney | Chafer | [email protected] | 2 | 9 | | Courtney | Watson | [email protected] | 1 | #N/A | | Dana | Bower | [email protected] | 1 | 10 | | Daniel | Jasak | [email protected] | 3 | 12 | | Daniel | Kozlowski | [email protected] | 4 | 13 | | Daryl | Marske | [email protected] | 3 | 14 | | David | Lee | [email protected] | 2 | 15 | | Derek | Russell | [email protected] | 4 | 16 | +-------------+--------------+-------------------------+-------+--------+With hundredths of a second apart it will depend on the format used and you may need to convert it to use it the visual correctly. The solution here might help:
Power Query will work a lot better with this without any additional formatting for a visual so i'd recommend using the aggregation there.
If I answered your question, please mark my post as solution, Appreciate your Kudos 👍
The dates are all formatted as "General Date" or "Date/time". I'll simply keep this at the back of my head that there may be issues and assume that what I can do in Power Query takes precedence. Thanks!