What is the difference between 2 sync buttons in backoffice 6.4?

[Former Member]

In the backoffice there is since 6.4 a new 'synchronize action' button which has less options. But besides the visual difference with the 'catalog synchronisation' button it looks like we have also another functional behaviour.

Is it possible that the second button does a full synchronisation and don't look after the records which need to be synchronised? Or is this a bug we are facing?

Anyway something weird is going on, I have done some tests

Test: synchonise action

Step 1. Nothing needs to be synced

• when running the "Catalog Version diff" no records are available

Step 2. start sync with 'synchonise action'

• when running the "Catalog Version diff" it is filled with records on the fly ==> NOK

• Our whole product catalog is synchronised ==> NOK

Test: catalog synchronisation

Step 1. Nothing needs to be synced

• when running the "Catalog Version diff" no records are available Step 2. start sync with 'catalog synchronisation'

• when running the "Catalog Version diff" no records are available

• nothing is synched as it should

Remark: we are using a specific sync user with some restrictions

[former_member677491 · Accepted solution]

Hi,

Synchronise action doesn't require for the user to provide all details which are available in catalog synchronise action. It was designed mostly for regular users whereas catalog synchronise action is for admin and person who want's to have more control.

All the settings you can define in 2nd step for catalog synchronise action can be controlled for synchronise action in local.properties

 # Synchronization config for backoffice
 backoffice.sync.config.createSavedValues=false
 backoffice.sync.config.forceUpdate=true
 backoffice.sync.config.synchronous=false
 # Available sync config values which override SyncJob settings. If not provided default values from sync job are taken
 #backoffice.sync.config.logToFile=true
 #backoffice.sync.config.logToDatabase=false
 #backoffice.sync.config.keepCronJob=true
 #backoffice.sync.config.abortOnColliding=true
 #backoffice.sync.config.logLevelDatabase=WARNING
 #backoffice.sync.config.logLevelFile=INFO
 #backoffice.sync.config.errorMode=FAIL

What I can notice is that Force Update by default is deselected(=false) in the wizard when for synchronise action it's set to true.

I would suggest to add to your local.properties:

 backoffice.sync.config.forceUpdate=false

However I was not able to reproduce your problem but this is the difference I can see at first glance.

[Former Member · Accepted solution]

Thanks for you info, I will check and give my feedback.

[Former Member · Accepted solution]

After changing this property it works fine. Thank you, this is very important as synchronising the whole catalog takes more or less a day. Is there some documentation on the abortOnColliding parameter?