Employee Center - moving Connected Content between instances

[Michal Sadowski]

Hi Employee Center superstars,

I'm getting ready for the migration project from Service Portal to Employee Center and just wanted to double check on one of the doubts I have that may impact the approach.

It's related to Connected content. Is this something you would start in Dev instance and then migrate up all the way to Prod for the initial implementation? Is this migratable in update sets or as XML imports or some other way? Any other thoughts on what to watch out for when moving Connected Content between instances?

Kind regards 

[Jacques Clement]

Hi @Michal Sadowski , long time no speak 🙂

IMO, this is something that was not thought through enough. The issue comes with a reference field called taxonomy_topic on the Catalog Item, that is automatically updated whenever you insert/update something in the m2m_connected_content.

So, you now have 2 bad options:

1. You XML export/import m2m_connected_content, but on your target instance, the business rule won't fire and this taxonomy_topic field on the connected Catalog Item will not be sync'ed. I don't know what the consequence is as I don't understand what this field is for
2. You capture this in an update set, but now you also capture the Catalog Item that maybe was being worked out and was not ready to go to the target instance just yet.

Here's the culprit: