# Dropdown List Not Displaying Data **URL:** \ **Category:** Ignition\ **Created:** [September 1, 2021, 6:39pm UTC](https://forum.inductiveautomation.com/t/dropdown-list-not-displaying-data/50533 "2021-09-01T18:39:32Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![TCARLSON](https://avatars.discourse-cdn.com/v4/letter/t/ce7236/32.png) [@TCARLSON](https://forum.inductiveautomation.com/u/TCARLSON)\ **Post date:** [September 1, 2021, 6:39pm UTC](https://forum.inductiveautomation.com/t/dropdown-list-not-displaying-data/50533/1 "2021-09-01T18:39:32Z")
I have a display with 31 dropdown list on it. This is used to modify a recipe. The display is acting strange though. Every now and then I will make a change on one of the dropdowns and the change will read correctly in the PLC but the text on this dropdown then changes to the text as if I have 0 value but the value reads correctly. Other times when I load a recipe a few of the dropdowns will display nothing at all. There is data in the PLC say value 38 which should read “Fill Tanks” but the dropdown will just be blank. Anyone have an idea as to why this is acting this way? ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [September 2, 2021, 2:45am UTC](https://forum.inductiveautomation.com/t/dropdown-list-not-displaying-data/50533/2 "2021-09-02T02:45:56Z")
I assume that the values that show blank are actually in the drop down’s dataset? How are you binding the value to the dropdown? ---
**Author:** ![michael2](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@michael2](https://forum.inductiveautomation.com/u/michael2)\ **Post date:** [September 2, 2021, 4:48am UTC](https://forum.inductiveautomation.com/t/dropdown-list-not-displaying-data/50533/3 "2021-09-02T04:48:47Z")
Try turning off search on the dropdown and see if that corrects the issue. That functionality can make text appear off screen for some reason. > [@\[IGN-5352\] Perspective Dropdown does not display values correctly if the dropdown isn't wide enough](https://forum.inductiveautomation.com/t/bug-perspective-dropdown-does-not-display-values-correctly-if-the-dropdown-isnt-wide-enough/48093/2): > > The ones on top are after searching? You can try play with the style overflow tho not sure if it will help. edit after test: Oh i see, once you select an option and then open up the dropdow again it indeed seems to space out to the left. This only seems to happen if search is enabled tho, the text gets pushed to the left so that the cursor is visible in the dropdown ---
**Author:** ![TCARLSON](https://avatars.discourse-cdn.com/v4/letter/t/ce7236/32.png) [@TCARLSON](https://forum.inductiveautomation.com/u/TCARLSON)\ **Post date:** [September 2, 2021, 1:36pm UTC](https://forum.inductiveautomation.com/t/dropdown-list-not-displaying-data/50533/4 "2021-09-02T13:36:02Z")
nminchin, The drop down has 100 custom properties. These custom properties are linked to step descriptions inside the PLC. I have the Data bound to the custom properties with an update cell function to fill out the data set with the custom properties. All properties have text in them non are left blank. Selected Value is bound the the PLC tag that holds the value. Nothing else on the dropdown has a binding. ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [September 2, 2021, 9:30pm UTC](https://forum.inductiveautomation.com/t/dropdown-list-not-displaying-data/50533/5 "2021-09-02T21:30:22Z")
> [@TCARLSON](#): > > The drop down has 100 custom properties That's a **lot of work!** to create all of those custom properties, all of the bindings on them, and all of the bindings on the cell updates. I don't know if it's the cause of your issue, but I can't imagine its helping. How often are these descriptions changing? If it was me, I would read in all of your tag values with a script in one read call and create the dataset in the script in a few lines of code. I would even consider reading the values using `system.opc.read` instead of having to create tags in the tag browser. Call the script when the mouse is clicked (or hovered over the component - I can't remember if on clicked works well or not for a dropdown component).