Product not connected to SKU after synchronization

Mauri Mitchell asked on August 5, 2020 17:57

We recently upgraded to Kentico 12.

We have multiple environments that we sync between, and all have been upgraded. Since the upgrade, we have been having an issue where the SKU gets unassigned on the destination server, despite being assigned on the origin.

For example, we sync a product page from our dev environment to test. Once synced, the product page is no longer assigned to a SKU on the test server. We have to login to the test server to manually assign the product to a SKU again.

Here is the message we get on the destination server: "This page is configured to be a product, however, it is not connected with any SKU yet. Use the action below to bind an SKU to the page."

How can this be resolved so that we don't have to reassign a SKU every time we syncronize?

Thanks,

Correct Answer

Juraj Ondrus answered on August 10, 2020 06:18

Just to add to what was already posted - what is the exact version? Have you checked the known and fixed bugs and/or tried applying the latest hotfix? I am asking because there was a similar bug fixed in hotfix no.8:

Staging - Relationship between products and pages broken after synchronizing pages
Synchronizing pages with an associated product (SKU) could break the relationship between the page and the product on the target server (in cases where the IDs of the given SKU were different between the staging instances).

So, applying the latest hotfix should fix this issue.

1 votesVote for this answer Unmark Correct answer

Recent Answers


David te Kloese answered on August 6, 2020 10:32

How did you apply the upgrade to the non-dev servers?

I think the connection between the pages is out of sync.

so your product page local has different ID's as to that same page on target. So when Kentico tries to map the product connection they are no longer identical.

Quickest test would be if you sync a NEW test-page with a NEW test-product can you update that one the next synchronization?

0 votesVote for this answer Mark as a Correct answer

Mauri Mitchell answered on August 6, 2020 15:41

Unfortunately I get the same outcome with a brand new product / page. Once synchronizing to the next environment, I have to reassign the page to the SKU on the destination server.

Can you provide more details on what you mean when you say the connection between pages is out of sync? How could this be resolved?

0 votesVote for this answer Mark as a Correct answer

David te Kloese answered on August 6, 2020 18:19

Well products and pages are stored as different objects (and tables) linked via an ID:

sql restult of node and sku

I believe those ID's should be resolved automatically and thus don't need to be identical. But that is what can't be synced.

Can you confirm the settings for ecommerce are set identical...

Are you syncing both the SKU and the Page and the same time? Does syncing one or the other first make a difference?

0 votesVote for this answer Mark as a Correct answer

Mauri Mitchell answered on August 14, 2020 17:07

The hotfix answer is correct. We were on version 12.0.0 and upgrading to the latest version resolved the issue. Thank you

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.