Valuelistvalues get lost...

We use application.setValueListItems to populate the valuelists used in our application.
Occasionaly smartclient users loose all valuelist entries, so values are displayed as return values and not as displayvalues anymore.

I already increased the client-heap as I was thinking of a memory problem, but this didn’t help yet.
I also looked at the memory usage when I saw this happening and this is approx. 60% of the assigned memory, so I think this can’t be the case.

Anyone familiar with this problem, or does anyone have suggestions to alter settings???

Thnkx for any input!

What type do the real values have? Are they UUIDs?
Are you sure you don’t change the values by mistake somewhere in the code?
What version of Servoy are you using?

A sample solution would be great, but it sounds like you didn’t find a 100% reproduceable scenario…

Marc,

1 question, is that valuelist that you alter there. somehow already loaded by a field before you alter it?

ok we did see a possible loop hole that could cause the behavior you are describing.

But only if the valuelist is first touched by something else then with application.setValueListItems

I fixed this in 3.5 and 4.1

Hi Andrei / Johan,

here are some answers to the questions you’ve asked:

Andrei Costescu:
What type do the real values have? Are they UUIDs?

These are VL like:
retVal → dispVal
1 → Todo
2 → Closed
3 → Wait for customer response

Length of the list seems not to be involved and… if this happens all valuelists will be gone…

Andrei Costescu:
Are you sure you don’t change the values by mistake somewhere in the code?

No, the setup routine will run at startup of the solution and won’t be executed for these valuelists.
We are actually populating other valuelists with ‘local’ values as we need them, but this are just a few universal named valuelists like:
‘localTxt01’, ‘localTxt02’, ‘localNum01’, ‘localNum02’, ‘localInt01’, ‘localInt02’
So we assign a valuelist to the corresponding type of field.

Andrei Costescu:
What version of Servoy are you using?

See my signature… 4.1.3 :)

Andrei Costescu:
but it sounds like you didn’t find a 100% reproduceable scenario…

you’re right… it’s even harder that I didn’t find this issue in eclipse… it just happens in the client. On the other hand: the clients are really used in production, I’m just coding, testing, restarting my devclient etc.

jcompagner:
1 question, is that valuelist that you alter there. somehow already loaded by a field before you alter it?

The valuelists where this behaviour occurs are ‘static’ and populated before they’re touched by anything else.
Please see also the above response on Andrei’s question.

jcompagner:
ok we did see a possible loop hole that could cause the behavior you are describing.

But only if the valuelist is first touched by something else then with application.setValueListItems

I fixed this in 3.5 and 4.1

Does this mean that is already shouldn’t be happening in 4.1.3, because it does… :(

No i mean i just fix it in 3.5.x and 4.1.x
So it will be in the coming release of both.

I guess we should just first test if it helps. its the only thing i could come up with.
And my best guess still is that you somehow touch it first
(doenst really have to be only the ui but also all the other getValueListXXX stuff on application)

jcompagner:
And my best guess still is that you somehow touch it first
(doenst really have to be only the ui but also all the other getValueListXXX stuff on application)

I will look into my startup order.

Anyway, I’m not sure if I was clear enough that we don’t have a problem setting the valuelists.
Valuelists do work always after fresh startup. We even can work for several hours, and suddenly all those valuelists are gone…

I guess setting them again will work, but didn’t write code to trigger that yet…

what you describe is exactly what i just fixed.
“At random times you suddenly after some time you loose the valuelist contents”

jcompagner:
what you describe is exactly what i just fixed.

Great! Thnkx Johan. Any planned release date yet?