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 records sometimes won't delete

Featured Replies

have a portal setup and sometimes, very rarely, but enough to be a headache, the line in the portal does not delete. When looking in the "lines" table, the record is in fact deleted, but it's still in the portal view. My clients can exit the database and when they log back in, it's gone.

I'm using the simple "delete portal row" script step.

i'm hoping other people have run into this same problem, and have a work around or perhaps i'm not doing something I should be.

First, try adding a commit record step. If that doesn't solve it, add a refresh window step, and if needed, select the "flush cached join results" option in the that step.

  • Author

I've tried that as well, perhaps my order is wrong.

my script is:

delete portal row ()

Commit Records

Refresh window (flush)

  • Author

well I think I have a workaround, at least so far in my testing.

I had to put a script trigger for a commit on every field in my portal.

I ran into this problem when our users were complaining that sometimes a portal row was not being deleted. Like @thejkfarr, I was running a script that included the delete portal row step with no dialog, followed by a refresh window step. Sometimes it simply didn't work - the bizarre thing was that you could step the script through in the Script Debugger, execute the Delete Portal row step, but the action was not performed, nor did Filemaker report an error.

In the end I rewrote the script so that I stored the UID of the portal record clicked, opened a new window off screen in the context of the portal's table, found the record with the stored UID, deleted it, closed the new window and then did a refresh window. This DOES work reliably.

What concerns me is that a script step will fail but does not report an error.

I've also encountered this. It could be a sign of a corrupted field index. Make sure the clients are all running the latest patch level of FMP.

It's not occurred for a while for me.

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.