Forum Discussion

pailong's avatar
pailong
Regular Visitor
9 years ago
Solved

DialGauge custom visual problems

Hello guys from a few hours it seems that DialGauge custom visual not working properly it happens to you?

thank you!

 

 

 

  • I have the same problem, the new update has caused it. Try deleting and creating them again, it worked for me.

     

    Edit: Add the pointer value and percentage after you have added all the other values, it seems to mess with the color limits if I put them first.

6 Replies

  • Greg_Deckler's avatar
    Greg_Deckler
    Community Champion

    Can you post some sample data, calculations and your DialGuage configuration so that we can recreate?

  • adri_s's avatar
    adri_s
    Frequent Visitor

    I have the same problem, the new update has caused it. Try deleting and creating them again, it worked for me.

     

    Edit: Add the pointer value and percentage after you have added all the other values, it seems to mess with the color limits if I put them first.

    • pailong's avatar
      pailong
      Regular Visitor

      Thank you all for the great support !!

       

  • v-qiuyu-msft's avatar
    v-qiuyu-msft
    Community Support

    pailongadri_sfriestad I can reproduce the issue like yours. After downloaded the sample of DialGauge visual, and opened it in the Power BI Desktop newest version 2.38.4491.282, the DialGauge displayed incorrectly. Once we recreated the DialGauge visual using the same properties as the existing one in the report, the new visual displayed correctly.

     

    To workaround the issue, you can use Power BI Desktop previous version 2.37.4464.602 temporarily. Meanwhile, you can send the feedback to author of this visual: [email protected] and let the author update the visual.

     

    Best Regards,
    Qiuyun Yu

     

    • dolney's avatar
      dolney
      Frequent Visitor

      I have the same problem, and recreating it does not work.  Re installed July PowerBI, works on the desktop but not on the published version. So sticking with a prior verison of PowerBI desktop does not solve the problem for my users.