Skip 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.

Go To Related Record

Featured Replies

Ok, this is driving me nuts.

Newly converted FMP5 to FMP8 solution. Lots of portals to other files, etc.

I generally have a "green button" on my portal rows to allow us to jump from, say, a jobs file with a task portal to each particular task.

Some of these simply used the "go to related record" button event, and some used scripts when I needed additional steps to be taken in FMP5.

Problem is, these two steps don't seem to work the same anymore? The button event takes me to the right record in the other file, as I expect, but the "Go to Related Record" script step does NOT take me there, or can take me there but only finds the first related script in the whole relationship instead of taking me to the exact related record the "green button" is on.

If I need to use a script (say, because I want to put a "commit records" script step in to start things off), do I need to make subscripts in the target files and crazy workarounds just to get to the right record?

and WHY OH WHY do these functions not work identically to each other?

Oddness. Thanks in advance!

Check the INDEXING on the key fields.

I did a 5 to 8 conversion a while a go and some of the fields did not index correctly even though they had always worked before.

Have you also rectified your file references yet?

See here.

  • Author

Awesome, thank you comment. I'll have to play with your suggestion. I never thought about committing records killing focus. I just eliminated my "commit record" initial step I've been putting everywhere to make sure to avoid "already being modified" records or later portals not being updated as we fly around our DB's... and it works as it should.

Idealdata, thanks for the help too; file references are clean as a whistle (that was my first clean up task) and I noticed that indexing was on "minimal" for my join field calculations for this portal and thought that might be screwing me up, but turning to "maximum" didn't help.

I think i'm going to go through for fun and kill all my old join calculations and just do complex relationships instead. Should speed things up I think!

Thanks again guys.

Create an account or sign in to comment

Important Information

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

Account

Navigation

Search

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.