PowerBi service not showing same data as in Desktop version

[svergara]

Hi all,

I made a report via PowerBi desktop querying information from our data warehouse and sharepoint. In order to adjust the data model to a star schema, I did some table transformations (e.g adding index columns, creating dimension tables, etc). When refreshing the data in powerBi desktop everything works well and the values displayed are accurate. However, when I publish this to PowerBi service and refresh the data using a gateway, the data is not mapped correctly anymore. For one specific filter it seems the index column is mapping the wrong values, and when appyling the same filters in the desktop and online version the results are different (being less in powerbi online).

I saw this piece of information but do not know if it is related to my issue since I do not get an error, only the mapping is done wrong online. 

What could be the issue in this case? Is there some configuration missing in the gateway that is not doing the mapping correctly?

Bests,

Sofia

[Anonymous]

Hi @svergara ,

Do you have any filter or measure involved with datetime?

Best Regards,

Jay

[PooBIDeveloper]

@Anonymous Why did you say so? I have datetime measure which changes the month value as the month changes. Could you please help as what could be wrong as we are also facing same issue.

[svergara]

@Greg_Deckler that is not the error, since even in default there are metrics showing different values compared to the Desktop version. 

[Greg_Deckler]

@svergara First thing to check is to reset your report in the Service. This is the Reset to default in the report header. This is the most common reason why things are different in the Service versus the Desktop.

[svergara]

I refreshed both, the service and desktop data sources and downloaded from PowerBi service the dashboard and dataset attached in order to compare both of them and saw the following: 

On the desktop version the following indexes are attached: 

while on the online version the indexes are: 

and this happens to all of the dimension tables in the model. I created the indexes by doing this: 

in order to follow a star schema. 

I have read that at times there are problems with NULL values in powerbi and since some of the columns presented them I converted them to a string value. However, this did not solve the problem.