What method are you using to update the global field? I would guess that you are using a script trigger and that the triggered script might benefit from adding a commit record step to it after the global field is updated.
Tried that just now but because its on object enter scripttrigger it prevents me from entering the field and seeing the valuelist.
the script is simply
Set Field[ValuelistFilter::Fieldname;Get (ActiveFieldName)]
Sometimes triggers get in the way of exactly what you are trying to do. That's why I asked how you are updating the global field.
If [not $$TriggersOff ]
Set Variable [$$FieldName ; Get ( ActiveFieldName ) ]
Set Field[ValuelistFilter::Fieldname; $$FieldName ]
Set Variable [$$TriggersOff ; True ]
Go To field [ $$fieldName ]
Set Variable [$$TriggersOff ; False ]
May work with some value lists, but I think those with the drop down arrow will still won't drop down properly.
I don't really see much advantage to your approach. I can still put all my values into tables so that I can "manage them all in one place", but use Manage | Scripts to name the value lists and specify their behavior so that I can then assign them to specific fields.
My approach lets me assign the managing value lists to a user without opening up the management functions of Filemaker.
I can assign value lists to a user without opening the management functions also and don't need to use your method as I can include logic in the relationship that controls the values displayed to match on a user list field in the value table so that the values are specific to the user.
How do you set the variable name in Go To Field?
I cant seem to do that.
I turned off the tab order on those fields and it seemed to help some if I click the drop down arrow more than once the list refreshes
I capture that value in the second line of the script. (And $$fieldname should really be $fieldname as it doesn't need to persist after the script terminates.)
thats not what I meant
In the dialog on Go to field how do I select that variable.
LOL thought that might be it.
Still no joy tried it with Go to Object
Ive tried a refresh window and flushing the cache and that didnt help much.
There has to be some trick to get it to recognize the global field change. If I simply deselect the dropdown arrow and reselect it the list changes.
Can you explain this other method you use.
The idea here was I could copy this field from a design layout Pallet and wouldnt have to change anything but the fieldname (and possibly some cosmetics) All the script triggers and valuelists would be in place. I wonder if adding the global field to this record rather than its own table might change things.
It's interesting to watch what happens if you enter the field while the script debugger is enabled. You'll see that the value list deploys before the trigger fires and this is why you method fails
The script works once you use go to object, but not if with the arrow. If you remove the arrow option, the value list deploys and displays the correct values.
I seem to recall that there isn't anyway to use a script to get a drop down list to deploy when the arrow option is specified.
I suppose you could create a button that looks like the arrow but is really a button with go to field specified.
Still doesnt work right even with out the arrow
If I click off the field anywhere and come into the field the list is the previous list. however if I follow the tab order things work ok