Product cockpit - initial sync is needed

[Former Member]

Greetings everyone,

We have two different product catalogs - one supplier catalog and one master catalog. Sync job, which I implemented, and not OOTB one, works well when it is run from the hmc or the backoffice, and it works well when I run a full sync.

The issue is when I create product via product cockpit, it can't be synced. It says that initial sync is needed. Could I somehow configure that to work without running full sync?

The flag is removed upon running single item sync from the hmc or when the whole catalog is synced (successfully, but when the job fails for validation reasons, it still requires initial sync).

[Former Member · Accepted solution]

Do you still use the same job for the sync?

[Former Member · Accepted solution]

I can not choose the job in product cockpit, there is a sync button which "does something", no output or sync happens. Left of that sync button are those status icons, and the one which indicates if a product is synced (red or green halved circle) is grey with a small exclamation mark saying "initial sync is needed". When I sync it from HMC, I can choose the job, if sync is successful, next time I can sync it via product cockpit which will use that same job then. I would like to skip the part where I have to sync it from HMC first.

[Former Member · Accepted solution]

BTW, if you were asking whether I am using OOTB sync job, I am not, I implemented my own. I updated my question.

[Former Member · Accepted solution]

I would understand what you describe if you would create a new job for each sync attempt. The sync descriptors need to be created first before the cockpit can display this item was synced before or not. However once you run it (the job), you should be able to synchronize any item independently regardless if it is a new or a modified item.

The OOB sync will work, try to find the difference between the two.

[Former Member · Accepted solution]

Yes, the warning is removed after I successfully sync the first product, any new or modified product can be synced. The issue is, initially, there will be no products in supplier catalog, the first one will be created and product manager will be unable to sync it. Default sync cannot be used as the one we implemented has some custom logic.

Can I somehow "fake" initial sync or create sync descriptors which will make it look like there was an initial sync?

[Former Member · Accepted solution]

Well, the supplier catalog needs to be created somehow (as well as the sync job). As part of the creation process you may also need to synchronize it. I haven't ever synchronized an empty catalog version, but it should work. If it does not just put some media item, or a category or something, that should not be a show stopper.

[Former Member · Accepted solution]

Thank you very much, your last proposal works, I just have to figure out how to run my sync job on initialization or server startup, first time only.

Best regards, Ante

[Former Member]

BTW it works for cmscockpit too. Thanks,