This is FM 11 Go, but I'm not sure if newer versions correct this or not.

 

I've got a form that is filled out via FM 11 Go and the file is hosted on a server, therefore an internet connection and a VPN tunnel is required in order to use the form.  Also, in this form I have an auto-entered serial number being used and tons of validation before the record is saved.

Now on top of all of this, it has been brought to my attention that gaps are appearing in the serial number, and the appearance of gaps is frowned upon by auditing.  The behavior is easily reproduced by doing the following:

 

1. Setup a FM file on a server with an auto incrementing serial number and some form of validation (a required value for example)
2. Connect to file via FM Go
3. Create record
4. Do not meet minimum validation to save record
5. Disconnect device from network
6. Connected to Database on another device and look at the auto-enter serial's next value and notice it is incremented

The other portion of the complaint is that the user starts a record, and any data entered is lost if they haven't met the minimum requirements and the internet connection is lost.

 

Now I can see several things to blame here and a few ways to attack it.

1. Blame the internet connection and make sure the connection is stable before proceeding (this is a hard requirement to expect end-users to maintain)
2. Blame the VPN and try to find a better solution than the VPN built into IOS (this will incur extra cost as well as more R&D)
3. Blame the server based file and build some hybrid local file that will transfer it's data to the server upon a solid connection (Complete rebuild and adds more complication than what is necessary and a lot more R&D)

 

So I'm not really sure how to logistically approach the problem as it seems to be a two part problem with variables that are way out of my control.  How is everyone else dealing with mobile data entry on these devices?

Set your serial number to generate On commit instead of On creation. Another thing to possibly look at is to enter the data into globals, then do the validation, and if everything passes validation write the record.

You can also commit records upon exiting a field to minimize data loss.

Set your serial number to generate On commit instead of On creation. Another thing to possibly look at is to enter the data into globals, then do the validation, and if everything passes validation write the record.

You can also commit records upon exiting a field to minimize data loss.

Changing when the serial number generates and committing the record on field exit may do the trick, thank you!