As we saw in this detailed review of what’s new in FileMaker 2023, one of the two flagship features, along with Perform Script on Server With Callback, is what Claris calls “Audit Log.”
There is so much to know about this feature that we preferred to dedicate a full post to it.
This is a very informative article – thank you!
Can you clarify something?
You say “In the case of drag and drop, this goes even further as you can actually modify a record while it is open by another user!”
However, I had not heard that before, and when I tested this, it did not seem to be true. If a record was open (either by editing or just with the Open Record/Request script step), and I tried to drag text into a field on a different FileMaker session, I got the normal dialog saying that another user was editing the record, and my drag-and-drop did not modify the record.
Is there a more specific scenario where drag-and-drop can modify a record that is open by another user/session?
Hi,
Thank you for your comment!
Indeed I cannot reproduce it. I’m pretty sure though that there was a way to modify a record like this. Maybe this has been fixed along the way without notice. Thank you for pointing out! I will update the article now accordingly.
Perhaps you are remembering the issue where drag-and-drop into checkboxes, radio buttons, and popup menus could insert data that was not in the attached value list?
That was definitely something many developers needed to be aware of. Pasting also accomplished the same thing, but drag-and-drop was something a user might even do accidentally. The solution for that scenario was to validate the field at the schema level in Manage Database options for the field, since both drag-and-drop and pasting still can get past layout-object-level “restrictions” like checkbox value lists.
That is still the case. You can still drag any value onto a popup menu.