Forum Discussion
Advocate IVCloudFronts' Dial gauge - colours not workign below 0
Hi
I'm using CloudFronts' custom dial visual, which was working fine until I changed the minimum value from 0 to -100.
I've used the 'Actual End' and 'Target End' values to get red, amber & green bands, but as I change the minimum value from 0 to -100, then -100 to 0 is coloured green, not red, as I would expect:
I've played with all the settings and colour, I've tried adding an 'Actual Start' of -100, but can't change the colour of the -100-0 band
It seems as though it's just taking the base colour, which is the green, but i would expect it to be red bacuase it's below the 'Actual End' value
I've raised it with CloudFronts, and I'm awaiting a response, but I just wondered if anyone has come across the same issue and if you found a solution
Cheers
Jim
Hi jimbob2285,
We appreciate your inquiry submitted to the Microsoft Fabric Community Forum.
Based on our understanding, the issue relates to how the CloudFronts Dial Gauge custom visual interprets color band ranges when the Minimum value is set below zero. In this visual, the red, amber, and green bands are calculated based on the configured thresholds such as Actual Start, Actual End, and Target End. When the Minimum value changes from 0 to a negative value, any range not explicitly covered by a defined band may inherit the visual’s base colour, which commonly appears as green. Consequently, the segment from -100 to 0 may display as green instead of red, even though, logically, it lies below the Actual End value.
Kindly follow the step below, which might help to resolve the issue:
- Ensure that the starting boundary of the first band is explicitly defined. For example, Minimum = -100, Actual Start = -100, Actual End = 0, Target End = your threshold value, Maximum = 100.
This configuration will ensure that the range from -100 to 0 is clearly treated as the first band.
Please find attached a screenshot and a sample .pbix file for your reference, as indicated below:
Since the CloudFronts Dial Gauge is a third party custom visual, its rendering behaviour is determined by the visual developer rather than the Power BI platform itself. As you mentioned, you have already raised the issue with CloudFronts, they will be best positioned to confirm whether this behaviour is expected or addressed in an updated version of the visual.We hope the information provided assists in resolving the issue. If you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.
- Ensure that the starting boundary of the first band is explicitly defined. For example, Minimum = -100, Actual Start = -100, Actual End = 0, Target End = your threshold value, Maximum = 100.
4 Replies
v-pnaroju-msftCommunity Support
Hi jimbob2285,
We appreciate your inquiry submitted to the Microsoft Fabric Community Forum.
Based on our understanding, the issue relates to how the CloudFronts Dial Gauge custom visual interprets color band ranges when the Minimum value is set below zero. In this visual, the red, amber, and green bands are calculated based on the configured thresholds such as Actual Start, Actual End, and Target End. When the Minimum value changes from 0 to a negative value, any range not explicitly covered by a defined band may inherit the visual’s base colour, which commonly appears as green. Consequently, the segment from -100 to 0 may display as green instead of red, even though, logically, it lies below the Actual End value.
Kindly follow the step below, which might help to resolve the issue:
- Ensure that the starting boundary of the first band is explicitly defined. For example, Minimum = -100, Actual Start = -100, Actual End = 0, Target End = your threshold value, Maximum = 100.
This configuration will ensure that the range from -100 to 0 is clearly treated as the first band.
Please find attached a screenshot and a sample .pbix file for your reference, as indicated below:
Since the CloudFronts Dial Gauge is a third party custom visual, its rendering behaviour is determined by the visual developer rather than the Power BI platform itself. As you mentioned, you have already raised the issue with CloudFronts, they will be best positioned to confirm whether this behaviour is expected or addressed in an updated version of the visual.We hope the information provided assists in resolving the issue. If you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.
jimbob2285Thanks for your response, this worked perfectly:
- I had already tried setting the [Actual Start] to -100 but by mistake I'd set it to -1
- And just couldn't see that it had changed, as the change was so visably small
- I'd created columns to divide my columns by 100 to show them as percentages
- And used the wrong column by mistake
- It now works as expected when i use the correct -100 value as the [Actual Start]
- Although I'm surpised the visual doesn't use a [Min] lower than 0 as the default [Actual Start] when not specified
Interestingly, CloudFronts responded to me and wanted to charge us £500 to fix a problem that didn't exist. Which I thought was a bit cheeky if it was a failing of their visual, and seems even more cheeky now that I know it does work was it should
Cheers
Jim
- Ensure that the starting boundary of the first band is explicitly defined. For example, Minimum = -100, Actual Start = -100, Actual End = 0, Target End = your threshold value, Maximum = 100.
- v-pnaroju-msft
Hi jimbob2285,
We would like to follow up and see whether the details we shared have resolved your problem. If you need any more assistance, please feel free to connect with the Microsoft Fabric community.
Thank you. - v-pnaroju-msft
Hi jimbob2285,
We are glad to know that your issue has been resolved. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.
Thank you.