Forum Discussion
PowerBi Dashboard shows different values from Desktop
We solve this:
In sharepoint we made the column originally with a column name of "Outcome" but it was renamed to "Result" at some point.
In powerbi desktop, we have the code "Last Completed Milestone = calculate(DISTINCTCOUNT('Sharepointsite - milestones'[MilestoneName]),'Sharepointsite - milestones'[Result] = "True")".
We made a connection to sharepoint using implementation 1.0 and it worked, but it also showed the column as "Result" and not the internal name of "Outcome".
When we published to powerBI service, it was using (what we guess) to be implementation 2.0 and it load the sharepoint site with the same colum being named "Outcome" and not the display name of "Result".
Because of this, the first measure would not be able to evaluate the logic and would result in no values. Because of this dependent measure returning no values, the next measure would return the else condition.
We solved this by just changing implementation to 2.0 (Was a bit of a pain) in powerbi desktop and rewriting the first measure to use the "Outcome" column. This solved the problem.
We solve this:
In sharepoint we made the column originally with a column name of "Outcome" but it was renamed to "Result" at some point.
In powerbi desktop, we have the code "Last Completed Milestone = calculate(DISTINCTCOUNT('Sharepointsite - milestones'[MilestoneName]),'Sharepointsite - milestones'[Result] = "True")".
We made a connection to sharepoint using implementation 1.0 and it worked, but it also showed the column as "Result" and not the internal name of "Outcome".
When we published to powerBI service, it was using (what we guess) to be implementation 2.0 and it load the sharepoint site with the same colum being named "Outcome" and not the display name of "Result".
Because of this, the first measure would not be able to evaluate the logic and would result in no values. Because of this dependent measure returning no values, the next measure would return the else condition.
We solved this by just changing implementation to 2.0 (Was a bit of a pain) in powerbi desktop and rewriting the first measure to use the "Outcome" column. This solved the problem.