Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×
The Claris Museum: The Vault of FileMaker Antiquities at Claris Engage 2025! ×

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

Recommended Posts

Posted

I've found an undocumented RecordOpenState (see attachement). The state is 3 and as far as I can tell it means "Record that you just deleted but is still showing on the layout because an OnRecordCommit trigger is stopping it from committing".

 

I post it for information and to see if anyone else has ever seen it. There seem to be some specific conditions required to make it happen as I can only make it happen on records created via a certain relationship at the moment. I'll report back if I can find out enough info to report it as a bug.

post-106054-0-47243600-1371641170_thumb.

  • Like 1
Posted

OK, to recreate, try this.

  1. Create two tables Parent (pk_parent, other_fields) and Child (fk_parent, other_fields)
  2. Link Child to parent via pk_parent and fk_parent and allow creation in the parent table
  3. Don't check "Delete this record when record is deleted in the other table"
  4. Go to the layout based on the child table and add some fields from the parent table.
  5. Create a new record in the child table and fill in the parent table fields to force the creation of a new parent
  6. Go to the layout based on the parent table and try to delete the parent record. Ideally do this with the script debugger running.
  7. In my system, as soon as the delete step completes, Get ( RecordOpenState ) is set to 3 and the record is still visible on the layout
  8. The record only disappears when a second delete action occurs or when a commit occurs.

Notes:

  1. I'm not sure the steps above will reproduce this as I've not had time to try it on a vanilla solution. There could be other factors I haven't considered in my solution that cause it.
  2. I noticed this because I am preventing commits until user presses save or cancel. Chances are you wouldn't notice the issue if you weren't catching commits using the OnRecordCommit script trigger that sometimes returns 0.
  3. I can't help thinking that this is somehow related to the bug where portal records sometimes don't delete if you try to delete them before committing them, which has existed since at least FM11 as far as I know. Perhaps fixing that will fix this...

This topic is 4232 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
×
×
  • Create New...

Important Information

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