SAP Knowledge Base Article - Preview

3023423 - Synchronization automatically triggered with forceUpdate by "Synchronize" action in Backoffice

Symptom

Triggering synchronization with ForceUpdate flag enforces synchronization of every item in source catalog version regardless of whether target items require update or not. In some cases number of unnecessarily synchronized items can be counted in hundreds of thousands or even in millions. Such synchronization can takes hours instead of expected minutes.

Below property was introduced into 'backoffice' extension in project.properties file around CX6.3, but it's not documented in help.sap.com documentation. It has ability to affect setup of forceUpdate flag in created synchronization cronjobs.
backoffice.sync.config.forceUpdate=true

It's purpose is to set forceUpdate flag to true as default value for synchronizations triggered from backoffice by "Synchronize" action (circling arrows icon ) on Catalog Version item.

This setup may lead to accidental startup of long running synchronization cronjob since full synchronization with forceUpdate always synchronizes all items between catalog versions defined in sync job. 


Read more...

Environment

All CX with backoffice (since CX6.3.0.6)

Keywords

syncjob force update long stuck synchronization  synchronize forceUpdate backoffice.sync.config.forceUpdate backoffice.sync.config TBD , KBA , CEC-COM-CPS-CAS , Catalog & Sync , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.