cancel
Showing results for 
Search instead for 
Did you mean: 

ml_remote_id Format

Former Member
3,190

I am doing sync from iPad (ULDB file) to Mobilink server. The ml_remote_id I have set in the client side is a integer (e.g : 888), but in the Mobilink log it is being recorded as "a9219090-6ab8-122b-8000-c82a14000858". What could be the reason. Any idea?

Former Member
0 Kudos

Could you please post the MobiLink server log file (please remove all sensitive data before post it)?

Former Member
0 Kudos

Just curious - why do you want to use a non-default remote id?

If it is for implementing a download subset, it would be better to use the MobiLink user ID or an authentication parameter.

Accepted Solutions (0)

Answers (2)

Answers (2)

jeff_albion
Advisor
Advisor

I would expect that you are likely setting the database option 'global_database_id' to '888', not 'ml_remote_id' - these are separate concepts/database options.


There is the database property 'global_database_id', which must accept an integer value. This value is used to determine the partitioning for a GLOBAL AUTOINCREMENT value (e.g. which range of values can be used for that particular remote).

The 'ml_remote_id' database option is instead used to uniquely identify a remote database in the MobiLink system - this is automatically set to a GUID value upon first synchronization if it has not been set previously. Notably, the 'ml_remote_id' value can take a string value (e.g. 'HR001'), not just integer values.

Former Member
0 Kudos

Try this:

-- Set the MobiLink remote ID: SET OPTION PUBLIC.ml_remote_id = 'Whatever you need it to be';

VolkerBarth
Contributor

...but take care of this warning, cited from here:

Caution

In most cases, you do not need to set the remote ID or know its value. However, in the event that you do need to change it, the safest time to change the remote ID is before the first synchronization. If you change it later, be sure you have performed a complete, successful synchronization just before changing the remote ID. Otherwise you may lose data and put your database into an inconsistent state.