The Mobile Check-In process attempts to update the MET/TEAM server’s database with the changes that were made to existing records and any new records that were created in the database on the mobile PC. This brings up the question of what will happen when changes are made to the same records, whether it is an Asset, Type, Work Order, Procedure, etc., on the server and on one or more mobile PCs, and then the mobile PCs perform a Check-In. The simple answer is that the change that was made last (most recently) ends up in the master database following a Check-In, regardless if that change was done on the master database or on one of the mobile PCs. It is also important to note that these updates are performed on an entire record in the database, not on individual fields within the record.

For example, if an Asset’s Warranty Date setting gets changed on the server, and then at a later time that same Asset’s Not Tracked setting is changed on a mobile PC, when the mobile PC performs a Check-In, the Asset’s Warranty Date will revert back to its original value and the Not Tracked setting will reflect the change made on the mobile PC (the mobile PC’s updates “win” because they were done more recently). However, if the Not Tracked setting on the mobile PC was changed before the Warranty Date setting is changed on the server, the Warranty Date setting will remain intact and the Not Tracked setting will not get updated on the server after the mobile PC performs a Check-In (the server’s updates “win” because they were done more recently).

Another thing to consider is that changes to the System Default settings on the mobile PC are never updated on the server after a Check-In.