This seems to be a bug to me, at least it's not behaving as I would expect.

Two tables Company and Event attendance. I create an event attendance record and want to apply a company to it by selecting the company from a portal. If you then use a button driven delete record request it deletes the company not the event attendance record even though the portal is set not to allow deletion of related records.It's ok if you click into space after selecting the company to put focus in the event attendance record or add a got to field[] step in the selection script so it's easily fixed but surely you shouldn't be able to delete a related record when the portal is set not to allow it ?

BugDemo.zip

I believe the portal delete setting only applies to the built-in delete record step, and can be overridden by a developer script. To ensure the record is committed prior to the delete step, just add a commit step prior to it in the delete button script. This will be more reliable than adding it to the end of the select script.

But why does it behave differently when focus is left in a portal row by clicking a button in a row to when focus is achieved by clicking in a field in a row ?

In these cases using the scripted delete behaves differently.

Hi Robert, I agree that it looks like a bug. It may be a side effect from a change in focus for some functions when operating on related records, as in a portal. You might check this discussion and Soren's reference for details on this:

http://www.fmforums.com/forum/showtopic.php?tid/171699

In this case, it looks like the solution is to make sure the record is commited prior to any Delete Request/Record[] script step.

Thanks for pointing out the problem.

[edit:] I'm still running FM8v1 Advanced. Is the bug still present in 8v2?

Edited February 1, 200620 yr by Guest

I have 8v2, and the behavior is the same.