I need to update a file located at a hosting service, adding a few fields (including containers) and modifying a couple of layouts. MirrorSync was previously set up by another developer. 

 

Do I need to re-run the whole MirrorSync process, over-writing previous settings, or is it possible to run the set-up in some manner just to update it, or ... ? 

 

Also, I noticed that there are two records in the MirrorSync table - does that seem right?

 

TIA,

debi

Hi Debi, sorry for the delayed response.

 

When you add new fields, be sure to go to the appropriate sync layout and add the fields to that layout as well.

 

After you make the changes to the server copy of the database, edit the MirrorSync configuration. Just walk through all the screens without changing anything. On the last screen where you copy and paste the MirrorSync script steps, go ahead and do that (replacing all the steps in the current MirrorSync configuration).

 

Once that is done, you should be set to go. Users with older offline files will still be able to sync with their older files (although they won't get the new fields or layout changes), and users who download new offline copies will get all the new fields and layout changes.

Thanks, Jesse. That is what I did and everything went pretty smoothly.

 

Still wondering about the number of records in the MirrorSync table, as that seemed to magically go up to three. Is that OK? Are there any issues related to adding/deleting records in that table?

 

TIA,

debi

It depends on what is in the 'type' field, which you can see when you switch to the 'internal' tab on the MirrorSync layout.

 

You should have one record whose type=server

For offline files that have completed the initial sync, there should be a second record whose type=client. This record should NOT exist on the server.

There may be additional records whose type=Temp. You can ignore those.

 

What are the type values for those 3 records in your case?

Jesse,

 

The data for the three type fields:

server

container

Hub

 

The mobile file is a copy of the served file; as this is from a third-party hosting service, we are unable to use the download feature. Type data is the same for both files, neither file has a type of client.

 

Thanks again for all the help,

debi

That's fine - the 'container' and 'hub' records are meaningless leftover records, you can keep them or delete them and it doesn't matter.

 

The download feature should work OK with hosting providers. Feel free to ask your hosting provider to contact us if they would like help setting this up for you.