Field in Portal, browse mode unchecked, doesn't fire any script triggers. Is this normal?
Is there a particular reason why you wanted the user to be able to trip a script trigger on a field where you've blocked browse mode access?
If you want the user to be able to click the field and perform a script, that can be done by using button set up to turn the field into a grouped object button that can perform the script that you were going to perform by tripping the trigger.
Ok, just looked at a Technical Brief posted and it says:
"if a field is configured not to allow entry in either Browse and/or Find modes, then an OnObjectEnter script trigger would only execute a script if the field is entered via a script step."
So guess that's the answer.
It was in an existing layout. Did have the grouped button/field, but couldn't get any triggers to fire. So tried ungrouping (don't really understand the grouping concept). Have a list of names and a master detail of their records. Trying to set a variable to a field value when a name is selected. Checking the browse mode, I can get the OnObjectEnter to fire.
Ok, just tried your suggestion and that works. I was trying to use the script triggers rather than setting it up like a button calling the script. Thanks.
Both making the field into a button or blocking access prevents the user events that trip one of those triggers. You can’t directly put the cursor into the field, modify data in the field nor move the cursor out of the field.
If you need to permit access to the field and have a script performed, allow field access. If you don’t want to permit access, but do want that script performed, make it a button.
And since you asked about grouped buttons: You can select multiple layout objects and make them a group by selecting that option from the Arrange menu. This enables moving and formatting the group as though it were a single object. The group can also be given an object name, conditional formatting and/or a visibility expression. Such group level settings are lost if you ungroup such a grouped object. Such options specified for objects that are part of a group remain in place and can be seen/modified thru use of the layout objects tool.
If you select one or more layout objects and then pick “button set up”, FileMaker creates an invisible button object and groups it with the selected layout object. Any button settings that you choose are applied to the group and are lost if you ungroup such a button. Like any other grouped object, you can see and modify the individual objects by using the layout objects tool
Thanks for taking the time to explain this. Makes it much clearer now as to what that does.
Retrieving data ...