Forum Discussion
Exported Underlying Data Mismatch
Does your sharepoint list make use of Version control? If so, are you making sure to exclude items that are not the latest version?
Are you excluding items that are not marked as "current", but your user is seeing items those items?
Does your sharepoint list make use of the publishing framework and is your user seeing items that are in draft mode which are excluded from power bi?
We are not using Sharepoint but the Power BI APP as the sharing interface for all corporate users.
Underlying data should not exclude items as you mentioned in your post if my understanding is correct. And based on my findings, the missing records actually occurs only on 2 specific sales rep out of total of 10 sales rep. The downloaded data was actually downloaded by myself who was an admin and another Key account user who has full access to the report data.
I have also try to download the report data directly from the workspace report and it return the same result with the same missing records.
- Anonymous8 years agoNot applicable
Ok so lets go back to basics. Where is the data stored and what import logic are you using? Is there anything within the import logic that could be excluding rows?
- roytap8 years agoHelper I
The source is from the SSAS cube.
The report and the cube are actually showing the correct value. But the underlying data is missing some records after i compare it against the source data and the report data.
If the import logic exclude the row, the report value should show the incorrect value which will be the same as the underlying data. But the report is showing the correct value in this case.
- Anonymous8 years agoNot applicable
The Power BI reports can only report on the underlying data in its own model, so if the data is being excluded in the underlying data, it cannot appear in the report itself. There must be another variable at play that is giving you the wrong impression either:
- The rows aren't in the data and shouldn't be there to get you the correct result.
- The rows are in the data but you haven't found them.
- The rows aren't in the data but there are other issues in the data as well that are causing you to get the correct answer for the wrong reason.