3 Replies Latest reply on Sep 3, 2014 9:00 PM by philmodjunk

    Can't delete portal row

    tomswell

      Title

      Can't delete portal row

      Post

      I've recently transitioned to FM13 and have just discovered that a previously functional delete portal row script

       [ button ] doesn’t work ? I've made sure the button is within row

      when looking at data viewer - Get(ActivePortalRowNumber) it always returns 0 regardless of what row I'm on ? 

      I've fooled with commit record and refresh with no good result

      this is a basic invoice / line items TO which otherwise functions as expected ?

        • 1. Re: Can't delete portal row
          philmodjunk

          There's been no change between versions with regards to this aspect of FileMaker. The delete portal row script found in the Known Bugs List, for example, has continued to function correctly when the file was converted from .fp7 to .fmp12 and continues to function correctly with FileMaker 13.

          Check and make sure that the portal setup option to permit portal row deletion is enabled if you are using the Delete Portal Row script step to delete the portal record, but what you report with Get ( ActivePortalRowNumber ) suggests that something is causing the clicked portal row to lose focus. Commit records is definitely a prime suspect, but maybe you have a script trigger that is also being tripped when you attempt to use this script to delete a portal row?

          • 2. Re: Can't delete portal row
            tomswell

            your so sharp ! there was a script trigger linked to portal that disrupted deletion. can you point me to knowledge as to the hierarchy of commands and triggers. I debugged several times never considering such as being cause for disruption.

            Thanks

            • 3. Re: Can't delete portal row
              philmodjunk

              Any script that interacts with the layouts may trip a script trigger. When such is tripped, the script that trips the trigger is paused, the trigger performed script runs to completion and then the paused script picks up where it left off--unless it ends with "Halt Script", in which case all paused scripts are halted right where they were paused.

              It's often useful to use a global vairable as a flag. All trigger performed scripts check the value of the variable and exit without doing anything if the script is set. You can then disable all trigger controlled scripts by setting the variable to a value.