3 Replies Latest reply on Mar 10, 2015 4:39 PM by philmodjunk

    Script trigger not working in a portal row

    ijontichy

      Title

      Script trigger not working in a portal row

      Post

      I have a filemaker 11 database converted to filemaker 13 and the script trigger works perfectly.   The same set up (as far as I can tell!) is not working in an organically made filemaker 13 database.

       

      What are the reasons why a script trigger might not trigger (onObject Enter) when in a portal row?

       

      Making me a weee crazy, this one.   Thanks in advance.

        • 1. Re: Script trigger not working in a portal row
          philmodjunk

          Don't know of any differences in behavior for this trigger between v11 and v13. But portals are a little bit different. Perhaps you have a layout object, such as a field that is floating above the portal row instead of "owned" by the portal? (If it's owned by the portal, it will move when you move the portal while in layout mode.) If so, entering this field does not enter the portal and then the trigger would not be tripped.

          • 2. Re: Script trigger not working in a portal row
            ijontichy

            Thanks.  It moves with the portal.   Just doesn't trigger.   I've worked around it by using button set-up instead.   If there are other things to try I'd like to hear 'em.   Because it really is identical to the older database and it simply isn't triggering and that's just a bit maddening. 

            But thanks!

            • 3. Re: Script trigger not working in a portal row
              philmodjunk

              As a test, I took a file created with FileMaker 13 that happens to have a portal.

              I selected the portal while in layout mode and used a right mouse click to specify that the onObjectEnter Trigger perform a simple script that uses a custom dialog to display the text "Hello".

              In Browse mode, I can click into any field in the portal row or press tab while in the field that precedes the left most field in the portal row.

              In both cases, the custom dialog appears as expected.