Jump to content

Pause Resume Script Step and Getting Current ID on Resume

This topic is 2572 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Hey Everyone, I've been doing a lot of Pause/Resume script steps in a solution and I've got somewhat of a hack for the task I'm trying to accomplish, but I'm wondering/betting there is a simpler solution. 


For example, the work flow works something like this. There are Three tables Invoice, InvoiceItems, and Products.


The user is looking at the Invoice Layout and adds a InvoiceItem. Then, they need to pick a reference Product. From this point, I have a button on the InvoiceItem record that says "Add Product". I run a script that shows another "pop-up" window with a List View of Products with pictures. The Script is Paused. Each record has a button that says "Select". Once the user presses the button select, the window will close and the the Product ID is linked to the InvoiceItem.


The trick is to get the Product ID before the pop-up closes and save it to a variable. When I have the "Select" Button with script Step Resume Script it doesn't seem to enter/access the listed record I am selecting and therefore when I try to set variable ProductID = $ProductID...$ProductID is empty or the wrong one. I have a few hacks to work around this by splitting the script into two scripts, but I'm not totally happy with the solution and I'd prefer to keep it all in the same script.


Any ideas?



Link to comment
Share on other sites

Each record has a button that says "Select".


And what is the action assigned to that button? If it's Resume Script, and if your script does:

Pause Script
Set Variable [ $productID ; Products::ProductID ]
Close Window [ Current Window ]

then you should be fine.

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

I've never liked Pause/Resume but used it because there was not better alternative...until Modal Windows! I suggest switching to making a New Window[] that can't be navigated away from and two scripts, one to start, one to end.


That's exactly my current solution! A modal pop-up. I was trying to keep it all in once script for ease of management of local variables.


I main issue was when starting the routine, I press a button from the parent record, I need to capture the parent record ID. The script ends. So I need to store the ID in a global variable or global field somewhere. This way, when I "resume"  I can inject the parent record ID back into the new related records that the user is creating. I just need to be careful to clear out the global variable/field when I finish the script. There are some other issues, but I've got a nice working solution and the clients are happy.

Link to comment
Share on other sites

This topic is 2572 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By BostonFM
      I am trying to script an import of three worksheets in the same Excel file. The 3 geographical regions worksheets are not structured the same, i.e. field name rows are not in the same place and are named differently.
      The script runs but stops to ask which worksheet to process.
      How do I create a variable/parameter in the script for it to proceed sequentially from worksheet 1-3 without stopping?
    • By HOnza
      This is a fresh story of me spending hours trying to fix a technical issue and accidentally revealing a gold nugget. A few days ago one of my nightly server-side scripts stopped working without any apparent reason. But when I tried to run the script in FileMaker Pro it worked just fine. I really needed a way to debug the script on the server.
      Read more here
    • By HOnza
      I noticed that one of the articles updated in the official FileMaker Knowledge Base on September 23, 2011 was explaining how to select a random set of records in a FileMaker database. I was wondering how fast the currently recommended technique is and whether Ican make it faster with the help of FM Bench. I tried to apply it to a set of 50,000 records of randomly generated data. Then I made it much faster…
      Read more in the original article
    • By HOnza
      This is the first example I was showing in my session Marvelous Optimizations at Pause On Error [x] London 2011. I already wrote about this optimization some time ago. It’s the one that led me to unveil the Marvelous Optimization Formula. You can find the original article here: FileMaker Script Execution Time Cut From 5 Hours To 6 Seconds
      I simply took the example and added FM Bench Detective into it to be able to exactly measure and examine what happens in the slow and the optimized script. Now you can watch the result in this video recorded at Pause On Error.
      Read more and download the sample file at honza.24uSoftware.com
    • By HOnza
      The second example I was showing in my session Marvelous Optimizations at Pause On Error [x] London 2011 was the script for selecting Random Set of Records. I found this example in the FileMaker Knowledge Base and optimized it to run at least 158 times faster when selecting 10 random records out of 50,000.
      This version of the example has FM Bench Detective script steps included to measure the original and the optimized script more precisely. Watch the video recorded at Pause On Error below to learn more details about this optimization.
      Read more and download the sample file at honza.24uSoftware.com
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.