This has been a somewhat consistent problem, but this instance of the flex repeater has been the biggest culprit. The behavior is extremely inconsistent, sometimes affecting one instance in the repeater, then upon reload, affecting a different one. To note, some of the unusual setup is due to it being the most stable behavior I could get it to.
Shown is the instances custom prop that uses a change script to write itself to the flex repeater (part of the unusual setup part, just having a direct binding was worse). The value and unit match what is shown on the screen.
After entering run time (same behavior happens in application) and out of it a couple of times, the following happens:
The custom prop instances is still identical to the first image, but the instances shown in the flex repeater props.instances change to still hold the defaultValue for the number and unit, but the actual shown value is now empty.
If I enter runtime and exit a few more times, sometimes it will show the correct values, sometimes it shows these empty/bad values.
Looking at the view used in the flex repeater, the params are input/output (this is due to needing to access the values to save the items to the database from the flex repeater view, and this same view works perfectly fine in other places).
I've attempted to replicate the same behavior inside the "Numeric Entry With Unit" view by copy/pasting the params from the flex repeater and starting and stopping repeatedly, but nothing unusual happens. (The change scripts on the unitParams.value and numericParams.value are used only for the unit conversion)
Best I can tell, the params in the flex repeater will sometimes get overwritten by the default param values in the assigned view since they are set to input/output, but inconsistently. This view works fine in other places with a similar setup, but for whatever reason continually has the above behavior happening, although maybe 25% of the time everything loads as it should. Any ideas on what may be causing this or how to resolve?