Bug: Home come value changed after loading into the model?

[Anonymous]

How is this happening??? I was trying to unpivot the table and loading into the report.

However, the value CHANGED after loading into the PBI desktop. 😫 Is this some kind of magic..?
Then how can I ensure the data accuracy...? No wonder the number never aligns, because the data is not accurate from the very first beginning....

[Anonymous · Accepted solution]

HI @Anonymous,

Query edit not really get data and save records to pbix file, it used to show the preview of processing result on current query steps and Datasource snapshot records.

For query editor previews, they weren't auto-trigger refresh to pull the latest records. (as notice panel said, your preview show processing result of 5 days ago Datasource snapshot data) 
When you apply saving changes and exit to query editor, it will auto turned on refresh on data model table records. (these operations will get latest records)
So your data view records not matched with backend query table previews. I'd like to suggest you do refresh operations on your query table side to get the latest records, it should fix the data not matched issue between backend and front.

Regards,

Xiaoxin Sheng

[Anonymous]

Hi,

This is not a refresh issue, it's a conditional column where value column is depending other column to show the status, especially, those are historical data for few months ago and data will not change no matter how many times I refresh.

Hope that clear this up.

[Anonymous]

HI @Anonymous,

So you mean this 'value' field is a conditional column based on other fields? If this is a case, which field it checks? Did it refer from other query table fields? Please explain more about these to help us clarify your scenario.

Regards,

Xiaoxin Sheng

[Anonymous]

Thank you Xiaoxin! I've figured it out, it was due to data changed somehow in the background, thank you for looking into this for me.

[amitchandak]

@Anonymous , This is strange. I can see a few replace value steps. Can you check if some of the replace value has caused it