I have an app in Filemaker Go where multiple people might sometimes edit the same record. Here's the issue:
User 1 goes and edits Record 1, but forgets to hit "Save", they simply go back to their Home Screen on their phone.
NOTE: Record 1is NOT locked in Filemaker when this happens.
User 2 edits the same record (Record ) and hits save
NOTE: this works and Record 1 IS saved in database with User2's data
User 1 opens Filemaker Go again
NOTE: they see sees the old data from last time they were in for Record 1, not the new data
User 1 goes to Record 2
RESULT: Filemaker automatically saves Record 1 with the OLD data that was on User 1's screen as soon as they leave Record 1, overwriting the newest data with old data
Are there any options that will fix this? Something that says "hey, when someone using Filemaker goes to another app insta-save? or When opening Filemaker Go, refresh screen before committing...
Do you have save automatically turned on in the layout property sheet? This would save record changes automatically when leaving a field but that “leaving” would have to be explicit in FMGo.
An alternative would be to set a script trigger on the layout that does a commit record when you leave that layout.
Or you could test for fields modified and not saved then either prompt the user or commit the record in a script.
I don't understand what this means. This is a Filemaker Go app, but even if I had FileMaker Pro users, it would just add one more commit right? It's a very lightweight app so that wouldn't matter.
This doesn't trigger when the iPhone returns to the Home Screen or another App, assuming this is what you mean:
So basically every time users modify a field save it? I'll have to test how that works with text fields on mobile... I think I did it once before and there was lag, so typing was next to impossible.
By default with the setting set, every time the cursor leaves a field the record is saved. A commit occurs. That’s kind of the safety net that FileMaker has had forever to make entry-level programming less error prone.
The problem is implicit commit only occurs when the cursor leaves the field where the data was changed. On FM go if a user changes the content of a field and then just moves on, not within the application itself, but move on to something else outside FMGo, then that record has never been committed. As far as I know, there is no good way to force a user to perform that commit if he just leaves FM go with the cursor in a field that has just been changed.
Maybe an on layout enter trigger, commit. Then the second user would save existing edits? Idk. Have to test that one out.
That's the root of the problem. It seems like when you leave FIlemaker Go it doesn't lock the record, but remembers your place, so when you reopen it, it just sets the record back to whatever it was when you were last in Filemaker go.
So I'm looking for a workaround for this bug. I was hoping there was some way to force it to save... I don't think there's a way for it to refresh BEFORE the screen loads...
So back to a training issue. You leave a record open with out saved changes, you risk losing those changes. Like walking away from a desktop without saving your doc and a power outage or system freeze hits.
[quote="Malcolm, post:8, topic:4833"]
It should be locked at the point that a user enters a field.[/quote]
Most of the data is triggered by buttons which update fields. So if a user clicks a smiley face the ToggleField Script sets it to 1, if they click on a medium face it's set to 0, and if they click on the frown it's set to -1.
I just added a commit to that script step.
A few of them are text fields... but they're the exception so hopefully that will help some... but not really because.
I wish it were that easy. The real problem is if you VIEW a record and either save it or don't and someone else edits if after you, next time you open Filemaker Go it overwrites it and reverts it to whatever was on your screen.
This server hosts multiple small applications, but if I can make the timeout for this particular app to a short period of time that might fix the problem.
I also (apparently) was using a fully patched, but old Filemaker Go 19 app. I just upgraded it so maybe this is an issue they've solved since then. I'm going to do some tests over the next day or two and see what I can figure out.
THAT is a real problem. I need to test that. I have literally dozens (maybe hundreds) of FMGo users and never experienced this before but maybe I missed it
OK sorry for the panic @Kirk the real problem was I was using FIlemaker Go 19 instead of 2025. I just tried it with 2025 and it works correctly without that problem. I'm not sure if this was always a problem with Go 19, or if it's the combo of server 2003 and go 19 or whatever... I also so rarely use go for anything I just didn't realize that I had two copies of FIlemaker Go on my device and was opening an old one...
