4 Replies Latest reply on Nov 18, 2014 10:54 AM by GerardBeutler

    Tabbing on iPad with iOS 8 in Portal with trigger of modify with Commit/Flush results in return to...

    GerardBeutler

      Summary

      Tabbing on iPad with iOS 8 in Portal with trigger of modify with Commit/Flush results in return to top record of Portal

      Product

      FileMaker Go

      Version

      13.0.5

      Operating system version

      iOS 8

      Description of the issue

      A change in a field that has a pop-up menu with a script trigger that performs a commit and flush results in top record being selected and activating the same field and popping up the menu.

      When this occurs the user needs to scroll through the portal to find the record that was just change to continue to the next field or next record.

      Steps to reproduce the problem

      Create a two table, mother-child.
      Build the relationships with add record.
      Create two layouts one that allows for tabs with tab, enter, return selected and the other with no tabbing.
      Create a value list for one of the fields.
      Create a script with commit and flush steps.
      Apply script trigger to all fields with the pop using modify and the others with exit.
      Start creating records using any field then do a popup modify not using the top record.
      When modifying a text field the script trigger is performed but does not go to the next field.

      Expected result

      Stay on the same record and go to the next field.

      Actual result

      Pop up take to top record, select the same field and activates the popup.
      In a text field the field is modify but does not go to the next tab field.

      The experience from FM Go to FM Pro are different results.

      Exact text of any error message(s) that appear

      No error displayed

      Workaround

      Do not use tabs in portal with script trigger and script of commit flush.

        • 1. Re: Tabbing on iPad with iOS 8 in Portal with trigger of modify with Commit/Flush results in return to...
          TSGal

          Gerard Beutler:

          Thank you for your post.

          When you commit and flush the results, your cursor is not active in any field.  Therefore, you need to capture the portal record (row) before committing and flushing so you can then return to the same portal record and go to the next field.  To do this, your script may look something like:

          Set Variable [ $PortalRow ; Value: Get ( ActivePortalRowNumber ) ]
          Commit Records/Requests []
          Flush Cache to Disk
          Go to Portal Row [ Select ; No dialog ; $PortalRow ]
          Go to Field [ <next field in portal row> ]
          Halt Script

          -----

          In step #4, after selecting the same portal row that you left, then select the next field.  Since the OnObjectModify script trigger occurs before the tab to the next field, you don't want to select the next field and then tab out of it when the script trigger finishes.  By placing the Halt Script at the end stops the ending tab from executing.

          Let me know if you need additional clarification.

          TSGal
          FileMaker, Inc.

          • 2. Re: Tabbing on iPad with iOS 8 in Portal with trigger of modify with Commit/Flush results in return to...
            GerardBeutler

            Why does the it go to the first record, activate and select with FM Go and with FM Pro it does not go to the first record, activate, and select the field? 

            If this difference occurred between Window and Mac when using FM Pro what would be done?

            The expectation is that it would be the same experience on BOTH platforms. 

            Not a consistent experience, I should not have to worry about this nuisance.

            Have a great day!

            Gerard Beutler
            Link-Net, Inc.

            • 3. Re: Tabbing on iPad with iOS 8 in Portal with trigger of modify with Commit/Flush results in return to...
              TSGal

              Gerard Beutler:

              FileMaker Pro will also be similar.  That is, if you commit the record, the cursor is not in any field, so if you go to the next field, it will select the first row in the portal.  There is something you left out in the description of your script.

              FileMaker Pro will not automatically jump to the next field when a value is selected in a field formatted as a Pop-up menu.  FileMaker Go will automatically jump to the next field when a value is selected in a field formatted as a Pop-up menu.  The script basics I showed above will work for these differences in both FileMaker Pro and FileMaker Go.

              TSGal
              FileMaker, Inc.

              • 4. Re: Tabbing on iPad with iOS 8 in Portal with trigger of modify with Commit/Flush results in return to...
                GerardBeutler

                Ok so maybe it does not got to the next field in Pro BUT it does not go to the top record  and select in Pro. 

                When it does this  in Go and the first record is not shown it will go to the top record requiring the user to scroll through the portal, this does not occur in Pro.

                Therefore the different experience.

                Have a great day!

                Gerard Beutler
                Link-Net, Inc.