Thanks Johan.
If I attach the method to ValueList working properly, but I can not pass the arguments to the method.
Now the question is how and when you pass the method arguments.
Thanks again.
Roberto Diez.
Interdata.
Argentina.
we pass the arguments for you: displayValue, realValue, record, valueListName
you cant pass any other, thats just the arguments the valuelist global method gets. (and not everything has to be set for a specific call, see the sample code)
Thanks again Johan!
What you explained is correct and works very well.
The problem is as follows:
I want to define a single method and to allocate it to various ValueList, therefore, as you call the method with different parameters values.
When I attach the method to ValueList in the developer, you can not change the values of the parameters, therefore, as I do?
I hope to be clear on what I’m asking.
Thank you.
Roberto Diez.
Interdata.
Argentina.
Hi,
I found out this post looking for ways to use the getDataSetForValueList and you were very helpful, so thought I could ask you about a problem I have with this.
I’m using getDataSetForValueList to load a valuelist, the problem is I need to activate this everytime someone sets some other parameter.
The list should be reloaded with the new filtered values, problem is it is not being reloaded.
When debuggin, returned data is correct, but it seems as if Servoy doesn’t care for the changes, it is still showing the old valuelist items.
Should I post a bug issue or is this flexibility not supported??
Do you know some workaround for this?
Lambert, I do… too bad this is not fixed yet.
One thing though, am I suposed to call my getDataSetForValueList each time I change the dataprovider value??
For example:
oldValue = dataprovider value
dataprovider value = -1
getDataSetForValueList
dataprovider value = oldValue
getDataSetForValueList
One thing though, am I suposed to call my getDataSetForValueList each time I change the dataprovider value??
No, you are not. Servoy does that for you automatically when the realValue of the dataprovider changes to a value that is not contained in the current valuelist.
Setting the realValue to null does not have that effect.
@Hans : Thanks for making the feature request.
We find the globalMethodValuelist very very powerful…