Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Portal Rows

Featured Replies

Hi All

I am having a hard time with this. Any help would be highly appreciated.

I have a layout that has 2 portals. I want to loop thru the second portal which is physically located below the first one.

When I select "Go To Portal Row (Next)" in my script, it goes to the next portal row of the 1 portal.

Any suggestions : Please

Thanx in advance..

Just put in a "Go To Field" script step before the "Go To Portal Row" script and make sure the field is one that is in the second portal, not the first. Once the script is operating in the second portal, "Go To Portal Row" will go to the next row in THAT portal.

As the expert on ScriptMaker on the web I must warn you about using ScriptMaker scripts. ScriptMaker is single-threaded which means it handles just one script event request at a time and, unless FileMaker has changed it in version 7, subsequent near-simultaneous requests do not get processed. This is further complicated with the inability of the web language to recognize that a script event has not been processed. While many of the scripts used in IWP are fairly simple (e.g. go to layout) and are highly unlikely to cause a problem with near-simultaneous requests, more complex scripts can become problematic. A looping script is the very worst and can tie up the database such that other users become locked out. If you must rely on such troglodyte methods as ScriptMaker you had best test them rigorously for near-simultaneous requests - unless your development is going to be used by only one client. For rigorous testing I recommend several attempts to make near-simultaneous requests from a minimum of six browsers.

Many of us consider FMP7 a huge step backwards. Considering that FMP7 has abandoned the custom web abilities, it is extremely unlikely that FMI has addressed the single-thread ScriptMaker issues. FMI would rather that their db's not be served on the web.

When you say that near-simultaneous requests do not get processed, does that mean that other users trying to initiate the same script as the one just started will be unsuccessful, or that the first request will mess up and not complete the script, or that they both won't work?

" When you say that near-simultaneous requests do not get processed, does that mean that other users trying to initiate the same script as the one just started will be unsuccessful,"

Who said anything about the same script? I spoke of the shortcomings of ScriptMaker and the need for rigorous testing by the developer.

"...or that the first request will mess up and not complete the script,"

An event which is processing will complete.

"... or that they both won't work? "

Rigorous testing will reveal the answers for your solution. You need just one machine, but you need at least six browsers opened to make near-simultaneous requests. They do not need to be on the same scripts. If you are using a looping script you need to test that as well in this rigorous manner. And you may need to do it more than once. And you definitely need to compare the results/error pages in the browsers with the db files upon which the requests are made.

It can be a lot of fun. Enjoy.

Create an account or sign in to comment

Important Information

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

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.