Izan Posted July 7, 2017 Posted July 7, 2017 Hi Everyone, hope you are all fine.. We have set up our database and seem to sync fine from a ios device. When the fresh file was downloaded to ios device.... when a new record was created the device id was displayed/identified as: 1.001.. The second record was created from ios device and the record id was displayed/identified as: 1.002 .. We then developed/changed the main file on the server and re-distributed the file from there to the ios device again... when creating the next record from the ios device, the record id is: 2.003. The question is, why did the device id change from "1" to "2"? Is this normal? The problem we foresee is, if we continue developing and re-distributing the updated file, soon the device id will be 100 or even 1000.... Hupe my question is clear... Thanks in advance Izan
Jesse Barnum Posted July 9, 2017 Posted July 9, 2017 This is normal. Every time a new offline file is synced for the first time, it gets a new unique and sequential database ID. Since these are unique, it's fine to combine them with a serial number like you're doing to generate a new primary key. I don't see why it's a problem for the device IDs to be 100, 1000, or 50000. If you want shorter numbers, you might want to look into the writeback feature of MirrorSync: http://docs.360works.com/index.php/MirrorSync_advanced_topics#Write-back_values_for_user-visible_numbers
Recommended Posts
This topic is 2694 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now