# Flex Repeater Missing Output Parameters **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [March 26, 2025, 4:23pm UTC](https://forum.inductiveautomation.com/t/flex-repeater-missing-output-parameters/104258 "2025-03-26T16:23:24Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Sean\_LaFleur](https://avatars.discourse-cdn.com/v4/letter/s/d26b3c/32.png) [@Sean\_LaFleur](https://forum.inductiveautomation.com/u/Sean_LaFleur)\ **Post date:** [March 26, 2025, 4:23pm UTC](https://forum.inductiveautomation.com/t/flex-repeater-missing-output-parameters/104258/1 "2025-03-26T16:23:24Z")
I am using a flex repeater to get user input from a dropdown, but when the return values are unchanged, they disappear from the flex repeater instances array. The view takes in a Prompt\_Id parameter, which is then used to run a query that gets the values and labels for the dropdown, as well as the title for that instance. This is down via a property binding script transform on custom property Prompt\_Id that then sets custom properties Prompt\_Options and Title. The dropdown instances are then bound to Prompt\_Options and the title label is bound to Title. The output is set using a query script transform that takes in value from the dropdown and Prompt\_Id to convert the query, title, value, and label into a dictionary for the output parameter Prompt\_Options. In some cases, Prompt\_Id will be different, but the other variables don't change because of their use cases in the database and eventual export. When this happens, the flex repeater does not read the variables, and Prompt\_Options does not show up in the instances of the flex repeater. I have tried setting the Prompt\_Options output to an empty dictionary before building the correct dictionary, but this does not seem to help. In the end, this will be a nested flex repeater but I need to figure out this first level and that will more than likely help me fix the second level as well. I talked to ignition support for around 4 hours and they could not figure anything out. They ended up suggesting message handling which seemed to be a good option at first but after digging deeper and working with it more there's a lot of timing issues with the work I am doing. Any suggestions will be greatly appreciated. ---
**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\ **Post date:** [March 26, 2025, 5:44pm UTC](https://forum.inductiveautomation.com/t/flex-repeater-missing-output-parameters/104258/2 "2025-03-26T17:44:45Z")
Try my [Flex Repeater +](https://docs.mussonindustrial.com/ignition/embr-periscope/components/flex-repeater-plus/) component and see if it behaves differently. The way it handles input/output parameters is very different from the native component. ---
**Author:** ![Sean\_LaFleur](https://avatars.discourse-cdn.com/v4/letter/s/d26b3c/32.png) [@Sean\_LaFleur](https://forum.inductiveautomation.com/u/Sean_LaFleur)\ **Post date:** [March 26, 2025, 7:04pm UTC](https://forum.inductiveautomation.com/t/flex-repeater-missing-output-parameters/104258/3 "2025-03-26T19:04:25Z")
Thank you for the quick reply. My company would prefer to stick with the built-in Ignition components if possible.