Transfer catalog items using update sets

  • Release version: Australia
  • Updated March 12, 2026
  • 1 minute to read

    • Transfer catalog items published through Catalog Builder from one instance to another easily by using update sets automatically created for the catalog item. For example, you can transfer catalog items created by a business user from a non-production to production instance.

    Before you begin

    You can access update sets for a catalog item only if it is created or modified in Catalog Builder.

    For information on creating a catalog item in Catalog Builder, see Create a catalog item using a template.

    For information on editing a catalog item in Catalog Builder, see Edit a catalog item in Catalog Builder.

    Role required: catalog_admin, catalog_builder_editor

    Procedure

    1. Access an update set for a catalog item by navigating to All > System Update Sets > Local Update Sets.
    2. Search for the update set by the name, CB_<Template Name>_<Catalog Item Name>_<Date and Time Stamp>.
      Note:
      If a catalog item contains related records such as Variables, Variable Sets, Available For, or Not Available For in a scope other than the current item scope, then such items are transferred in a batch where the related record update set's parent field is set as the update set of the parent catalog item. For more information, see Update set batching.
    3. Transfer the completed update sets from the source instance to the target instance.
      For more information, see Update set transfers.
      Note:
      If you want to set the prefix of update sets, use the glide.sc.cb.item.update_set_prefix property. The property defines the naming format for catalog item update sets. You can use a static name or optionally include the following variables: ${template_name}, ${item_name}, and ${timestamp}. Format example: CatalogItem_${item_name}_${timestamp} Default value: CB_${template_name}_${item_name}_${timestamp}