Copying a catalog item to use as the basis for a new catalog item

[Mike LHCG1]

I need to copy a catalog item to use as the basis for a new catalog item which will have a lot of similarities. When I copy it, do I need to have a current/in process update set to capture the copy?

[Dr Atul G- LNG]

It would be better to create a new update set, as you are going to make changes in the copied version.

[Tanushree Maiti]

Hi @Mike LHCG1 ,

Similar requirement multiple times we have received from businesses of our client.

Create a update set-> make that current -> then copy the catalog item

using update set , you can move it to next instance (Dev->Test)

[DivyV]

Hi Mike, good instinct to ask before you start — this one trips a lot of people up.

Quick answer on the update set: yes, make sure you have a current/in-progress update set selected before you copy. The copy creates new records (the catalog item and its related config), and those get captured into whatever update set is active at the time. If none is set, your work can land in Default and be a pain to move later. So set up a dedicated update set first, then do the copy.

The bigger thing to watch for: how you copy matters. If you just open the existing item and use "Insert and Stay" from the form context menu, that clones the catalog item record itself — but it does NOT bring along the variables, variable sets, UI policies, or catalog client scripts. Those are separate related records, and people often don't notice they're missing until the new item behaves oddly. A few ways to handle it depending on what you need:

Option 1 — Insert and Stay, then rebuild the extras. Fine if the item only has a couple of variables. Copy it, then manually recreate the variables/UI policies/client scripts on the new item.

Option 2 — Use Variable Sets. If both items genuinely share a lot of variables, put the shared ones in a Variable Set and attach that set to both items. Then you maintain them in one place instead of duplicating.

Option 3 — XML export/import. For a fuller clone, right-click the item record and Export > XML, then import it. This is more involved and you'll want to fix up names/sys_ids, so I'd only reach for it if the item is complex.

Whichever route you take, I'd build and test it in a sub-prod instance first and click through the new item in the portal to confirm every variable and policy carried over. Happy to walk through any of these in more detail if you get stuck — good luck with it!

[Srikanth_9]

Hi @Mike LHCG1,

Create a new update set and mark it as current, copy the catalog item. Move it to the asked/requested instance. 

If the provided solution is useful/working, please Accept as Solution and hit the Helpful. 

Thanks & Regards,

Srikanth Akula.