Catalog UI Policies not working properly moving via Update Sets to another instance

[Marlon Dale]

So I've been having a nightmare promoting update sets across instances with Record Producers that have edits done in Catalog Builder, and some edits in the normal backend. UI Policies for one do not seem to function properly when moving via Update Set to a new instance despite having a successful import. Anyone else experience this? Not to mention getting duplicate variable sets, catalog client scripts, and catalog UI policies when the system generated Update Sets are moved with the user made ones after clicking "Add to Update Set"

[Peter Bodelier]

Hi @Marlon Dale,

I think the issue lies in the way you are working.

You will have to decide on using either Catalog Builder or Backend.

Personally I prefer using the backend as well, which doesn't create draft/published versions which may be confusing.