Forum Discussion
Bug: Data from Power BI Dataset differs when connecting using AS and in Direct Query Mode
Thank you for looking into the issue.
No. The source of data is the same. Only the connector and connection mode differs.
I introduced an index column in the table of original dataset and introduced it as the first column in the import query that used AS connector (to avoid aggregation).
This resulted in matching values/ entries.
There are null values in some numeric columns which could have caused problem during aggregation.
I tried replacing null with zeros in the original dataset. But for some reason it didn't work!!!
I m not sure what is causing the issue.
But the work around of introducing a primary key column as the first column in the AS query seems to be working for me now.
Thanks & regards,
Mannu
Hi Anonymous
From what you have put above there is clearly a difference between the 2 data sources.
What happens if you create a report to each one individually, do you get results that match?
If they do match then when you are bringing them together something is making the data change?
Thank you for looking into the issue.
No. The source of data is the same. Only the connector and connection mode differs.
I introduced an index column in the table of original dataset and introduced it as the first column in the import query that used AS connector (to avoid aggregation).
This resulted in matching values/ entries.
There are null values in some numeric columns which could have caused problem during aggregation.
I tried replacing null with zeros in the original dataset. But for some reason it didn't work!!!
I m not sure what is causing the issue.
But the work around of introducing a primary key column as the first column in the AS query seems to be working for me now.
Thanks & regards,
Mannu