# Bug: Value shows min from slider instead of tag value when navigating **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective\ **Created:** [October 3, 2023, 4:19pm UTC](https://forum.inductiveautomation.com/t/bug-value-shows-min-from-slider-instead-of-tag-value-when-navigating/79986 "2023-10-03T16:19:38Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Henry\_Neves-Charge](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/henry_neves-charge/32/41949_2.png) [@Henry\_Neves-Charge](https://forum.inductiveautomation.com/u/Henry_Neves-Charge)\ **Post date:** [October 3, 2023, 4:19pm UTC](https://forum.inductiveautomation.com/t/bug-value-shows-min-from-slider-instead-of-tag-value-when-navigating/79986/1 "2023-10-03T16:19:38Z")
![ezgif-2-626814b0c1](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/2/123367cde9b98a24f8f33dfcd465f6c0d954228c.gif) I have built a custom slider which works fine except when the value is bound to a tag and there's a minimum set that isn't 0 on the slider. As you can see from the video, on initial page load (refresh) the value shows correctly. However, if I navigate from another view the value shows the "min" value which is set on the slider, in this case 10. If I don't bind the value to a tag then it works fine. Any ideas? ---
**Author:** ![Henry\_Neves-Charge](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/henry_neves-charge/32/41949_2.png) [@Henry\_Neves-Charge](https://forum.inductiveautomation.com/u/Henry_Neves-Charge)\ **Post date:** [October 3, 2023, 4:23pm UTC](https://forum.inductiveautomation.com/t/bug-value-shows-min-from-slider-instead-of-tag-value-when-navigating/79986/2 "2023-10-03T16:23:44Z")
Huh, what's really strange is if I bind the minimum value to a tag as well then the problem goes away... ---
**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\ **Post date:** [October 3, 2023, 4:31pm UTC](https://forum.inductiveautomation.com/t/bug-value-shows-min-from-slider-instead-of-tag-value-when-navigating/79986/3 "2023-10-03T16:31:06Z")
> [@Henry\_Neves-Charge](#): > > and there's a minimum set that isn't 0 on the slider. I suspect your original post got garbled. Should this be, "and there's a non-zero **value** set on the slider". Maybe clarify by stating the values for `value : ` `min :` `max :` ---
**Author:** ![Henry\_Neves-Charge](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/henry_neves-charge/32/41949_2.png) [@Henry\_Neves-Charge](https://forum.inductiveautomation.com/u/Henry_Neves-Charge)\ **Post date:** [October 3, 2023, 6:18pm UTC](https://forum.inductiveautomation.com/t/bug-value-shows-min-from-slider-instead-of-tag-value-when-navigating/79986/4 "2023-10-03T18:18:26Z")
No, I meant when there's a non-zero **min** set on the slider. In the example above, the min is set to 10, max is 100 and then the value is bound to a tag "screen\_brightness". If I don't bind the value then it works as expected. Worth saying I've built this with embedded views. So it's a label there which is having the issue with its value. ---
**Author:** ![aaronrai24](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/aaronrai24/32/87248_2.png) [@aaronrai24](https://forum.inductiveautomation.com/u/aaronrai24)\ **Post date:** [October 3, 2023, 6:24pm UTC](https://forum.inductiveautomation.com/t/bug-value-shows-min-from-slider-instead-of-tag-value-when-navigating/79986/5 "2023-10-03T18:24:53Z")
I think I ran into a similar issue in the past, what worked for me was making a custom property that was bound to the tag, I then made sure this binding [transient](https://docs.inductiveautomation.com/display/DOC81/Perspective+Component+Properties#PerspectiveComponentProperties-PersistentProperties), I then bi-bidirectionally bound the slider value to the custom property, and that seemed to work iirc.