Hi team!:wave: <The new conditional formatting for...
# feature-requests
s
Hi team!👋 The new conditional formatting for Big Value charts is a great update! I have one request regarding this feature. Currently, we have to enter numbers manually, but it would be awesome if we could select other metrics or fields as thresholds instead. In our case, we often use Big Value for "Actuals" and want to change the color based on our "Budget" field managed in the data. It would be very helpful for tracking goals! Please consider it! Thanks!
✅ 1
p
👋 Thanks for your message - someone from the Lightdash support team will get back to you asap. Feel free to add any additional context to the thread here in the meantime (screenshots, app version if you're self-hosting etc.).
Hi Shota 👋 thanks so much for your kind words about the new conditional formatting for Big Value charts, and for the great suggestion ⚡ Being able to use another metric or field as the threshold (instead of a static number) would definitely be super useful for tracking actuals vs. budget and similar goal-tracking use cases. I've created a feature request for this: https://github.com/lightdash/lightdash/issues/20497 Feel free to give it a thumbs up to help us prioritize it 👍
s
Thanks! @Tori Whaley Much appreciated!
c
I've upvoted issue #20497 for you! This issue has been requested by 1 other user. I'll notify everyone here as soon as it's fixed.
m
Hey @s-tsuru, I had the same need last week to have a chart that compares the current KPI with the target, while you can't do it using a Big Value chart (at least for now) you can use the gauge charts for this. I think they work really well
👍 1
💜 1
lightdash scroll 1
s
Hi @Mahmoud Sellami , appreciate the tip! Actually, I was the one who requested the item selection feature for gauge charts 😄 Love how it turned out! Now I'm hoping Big Value charts can get the same kind of target comparison support — it would really complete the picture. Always nice to meet someone with the same use case!👏
🙏 1
cloudy 1
c
🗑️ Issue issue #20497 is no longer planned to be fixed.
No information provided
Check out the linked issue for more information.