Maybe someone had similar issue - dropdown (selection) values and choice values disappears after some time - probably after server has been in idle without visitors. After re-publishing the dropdown or choice element, it shows up again for some time.
What could be the issue?
What is DropDown list value .. are you using any kind of factory? can you check log?
Values are simply added in CMS in element itself. Only custom thing that comes from code is element block to render it differently. Also nothing interesting in logs...
Could you please provide more information about CMS version (UI), Forms version, Azure or on-premise ...?
We have a SupportCase report about this.
We will actively look into this immediatelly. Thank you.
This was happening on on-premise server with Episerver 9.12.2 and also after upgrade on 10.3.2. Forms version - 4.3.
Not yet tested on latest Episerver Forms packages.
Copied. Thanks for your info. Our QA cannot reproduce on Forms 4.4 and CMS 10.3, CMS UI 10.4.
But we will continue to investigate.
Hi, this issue AFORM-955 is fixed and resolved.
We will release hotfix Forms 4.2.2 (on nuget feed) for customer who currently use 4.2.1 (when this issue was initially discovered).
It will be merged to Forms 4.4.1 and above.
Any insights you can share? Where exactly was the issue?
In my opinion, it is not a good implementation of PropertyGenericList<T> (inside Forms).
It inherits PropertyLongString, and try to parse (JSON deserialization) underlying string (actual saved value) to a cached IEnumerable<T>. And no lock for the parsing/caching.
In some rare cases (Azure, I guess ...) the first request does not populate/deserialize string value (I don't know why), and it cache the IEnumerable<T>.Empty() as default value. Because nothing is updated in EditView, it keeps the Empty value all the time.
Because it is nearly impossible to reproduce it in development environment, we fix by rewriting it, and remove the cache of deserialization result, with a little bit of performance-sacrification, I think.
I see, thanks for insights. I can tell that it's not always Azure, we could reproduce it in AWS as well :)
When 4.4.1 could be expected?
It is in QA hand, under testing.