I an order system where I have a relation calculated value list based upon that a researcher has a head of department and depending what projects (cost centre) that head of the department carry the researcher can choose (only from that head of departments and no other heads projects) a project (cost centre) to debit the purchase.

The value list doesn't work unless it's "been triggered" by adding a new project... After a new project has been added the new project AND the already existing projects spring to live... I realize there is some relation error and mostly wonder if anyone has experienced anything similar?

Cheers!

The value list doesn't work unless it's "been triggered" by adding a new project

To me is it obvious that a relation needs a keyfield to work, and dynamic valuelist derived on relation condtions need them too.

Now primary keys can be unstored calc'fields but something is needed to give them values, such as layout rendering. But the safest bet is to set a real field via a script to get the condition changed there is some stickyness which requires some trickery...

Someone uses the webviewer to pull something like this off or place invisible fields in a portal like this:

http://www.kevinfrank.com/download/county-highlight-in-portal.zip

You need to post a file showing your problem, since there might very well be better methods to make your interface happen.

--sd

Hi Sören,

Many thanks for your reply!

I had a bad case of brain malfunction regarding this issue... Since I was working on my customers server I forgot that global fields do not store changes... I simply had to close the server sharing, open the file, add the permanent key and restart the sharing. I.e. prior to the action as above the creation of a new record added the key but only for that particular session...

Many thanks!

Thomas