I designed a valuelist (doctors) that takes its data from a table (operators), retrieving only the records marked as doctor.
I based the relation on a global having the value “doctor” on the left side and, on the right side, I selected the “operator_type” field.
The valuelist works fine if I use it on a field on a form, but it stops working if used attached to a field in a portal (exactly where I need it).
I tried to substitute the global with a calculation, but the result doesn’t change. Same thing if I change the portal from multiline to standard
Riccardino:
I designed a valuelist (doctors) that takes its data from a table (operators), retrieving only the records marked as doctor.
I based the relation on a global having the value “doctor” on the left side and, on the right side, I selected the “operator_type” field.
The valuelist works fine if I use it on a field on a form, but it stops working if used attached to a field in a portal (exactly where I need it).
I tried to substitute the global with a calculation, but the result doesn’t change. Same thing if I change the portal from multiline to standard
Am I missing something or is it a bug?
OSX.3.2; Servoy 1.2
I as able to reproduce this. I could correct the problem by listing the global.variable I was using as the primary key as coming from the table that holds the data displayed in the portal. If you list the global as coming from the table that holds the primary form data it will not work for displaying a value list in the portal.
Riccardino did have a wrong valuelist. It was based on a relation and there again a n-m relation on. That n-m relation it self was based on global variable. But if the first relation doesn’t return anything then the second (if if it is based on a global only (left-side)) will not be asked for its values..
So the only thing that had to be done was make the valuelist on the n-m relation (global relation) only.. So not going through another relation first..