Forum Discussion

Jordi's avatar
Jordi
Icon for Advocate I rankAdvocate I
10 years ago
Solved

Difference in gauges in Desktop and webapp?

Last week I created in PBI Desktop a testreport using de default gauge visuals, everything looked fine, but when i published it to the webapp, all the gauges where suddenly completely filled, while t...
Need Help
  • Jordi's avatar
    Jordi
    10 years ago

    Hi Mike,

     

    Yes it is the same data. Confirmed by the fact that it still occurs when I delete the data&report in webapp en republish it all again.

  • Jordi's avatar
    Jordi
    10 years ago

     

    Strange things....

    There was a update for BI Desktop, installed it, and.... now the problem was consistent: The desktop app and web app showed the same (wrong) full gauges. :smileyfrustrated:

     

    But the I found the solution:

    In the pictures can be seen that I used 2 times the same value for "max value" and "target value", apperantly something changed so this caused the described behaviour. (In my case, max value and target value are the same)

     

    I deleted the value for "max value" and voila, everything is ok now.

mikes2nd's avatar
mikes2nd
Icon for Helper I rankHelper I
10 years ago

I think your not on the same data. 

 

In report services it is using a different data source than your desktop.

 

 

  • Jordi's avatar
    Jordi
    Icon for Advocate I rankAdvocate I
    10 years ago

    Hi Mike,

     

    Yes it is the same data. Confirmed by the fact that it still occurs when I delete the data&report in webapp en republish it all again.

    • Jordi's avatar
      Jordi
      Icon for Advocate I rankAdvocate I
      10 years ago

       

      Strange things....

      There was a update for BI Desktop, installed it, and.... now the problem was consistent: The desktop app and web app showed the same (wrong) full gauges. :smileyfrustrated:

       

      But the I found the solution:

      In the pictures can be seen that I used 2 times the same value for "max value" and "target value", apperantly something changed so this caused the described behaviour. (In my case, max value and target value are the same)

       

      I deleted the value for "max value" and voila, everything is ok now.