Forum Discussion
Mixpanel API call returns different row counts on desktop and service
- 1 year ago
Found the issue myself, it was a combination of a hidden filter and one of the many gotchas with PBI.
TL;DR: There was never an issue with fetching the data.
If you have a text column containing the values "TRUE", "FALSE" and blank(), once you do a data refresh in the service PBI is so kind that it automatically transforms "TRUE" and "FALSE" into -1 and 0. Combine this with a hidden filter where "TRUE" and blank() is selected and voilá, it looks like you are getting fewer rows since you now only see the rows that matches blank().
This behaviour is documented here: https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-data-types#truefalse-type
Oh, and if you want to understand why logical true is represented as -1, start here:
https://stackoverflow.com/questions/23832703/why-does-forth-return-1-as-a-flag-for-true
Found the issue myself, it was a combination of a hidden filter and one of the many gotchas with PBI.
TL;DR: There was never an issue with fetching the data.
If you have a text column containing the values "TRUE", "FALSE" and blank(), once you do a data refresh in the service PBI is so kind that it automatically transforms "TRUE" and "FALSE" into -1 and 0. Combine this with a hidden filter where "TRUE" and blank() is selected and voilá, it looks like you are getting fewer rows since you now only see the rows that matches blank().
This behaviour is documented here: https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-data-types#truefalse-type
Oh, and if you want to understand why logical true is represented as -1, start here:
https://stackoverflow.com/questions/23832703/why-does-forth-return-1-as-a-flag-for-true