FileMaker Go and iOS 7 Bug | Paperless Archaeology
Nice explanation for the iOS 7 issues from John Wallrodt:
FileMaker To and iOS7 Bug
by John Wallrodt
September 16, 2013
According to FileMaker there is an issue between iOS 7 (due to be released on Sept 18) and FileMaker Go that affects the creation of a unique UUID number, which has the potential to wreak havoc on databases that rely on that unique number for syncing. This bug hits our own databases, as well as the copy of the database that is hosted at this blog.
Syncing from multiple copies of a database requires that each record have a very unique number. This is more than a straight serial number, since two separate copies of the database can each create a record in the same table which would give them the same serial number. Instead, our database relies on something more specific, a UUID which is generated from several types of information.
The UUID that we use is a custom function written by Jereme Bante a few years ago named UUID.New. It creates a unique number for each record based on:
more… FileMaker Go and iOS 7 Bug | Paperless Archaeology.
September 20, 2013 @ 2:19 pm
Yours custom function is based on Get(NIC) which on iOS 7 returns 02:00:00:00:00:00 for every device.
I recommend using Get(PersistentID) instead NIC. Get(PersistentID) showed same issue. This was fixed with current FM Go v12.0.8.
Take note that PersistentID on iOS 7 will change when FM Go App gets re-installed!
read the story:
Business Minute #5 - FileMaker Pro Gurus
September 27, 2013 @ 9:54 pm
[…] case you missed it, there is a problem with iOS 7 and FileMaker […]