Global widgets and application-level JavaScript extensions may be assigned to multiple sites. Because site IDs can vary between instances of Commerce Cloud, site associations for these assets are not included as part of the export. Instead, the site associations should be reconfigured after the assets have been imported to the new instance.

Note: See the Developing Widgets guide for more information on global widgets and application-level JavaScript extensions.

For page layouts, a sites array property is added to the exported data for each layout. If a layout is associated with one or more sites, Commerce Cloud exports the following values for each site:

The following shows an example JSON fragment for a layout that is associated with two sites:

{
  "displayName": "aboutUsUK",
  "pageTitle": "About Us UK",

  "sites": [{
    "productionURL": "www.cloudcommerce-uk.co.uk",
    "name": "Commerce Cloud Site",
    "repositoryId": "siteUK"
  },
  {
    "productionURL": "www.site2.com",
    "name": "Second Site",
    "repositoryId": "site2"
  }
]
}

During the import process, Commerce Cloud attempts to match the sites associated with a layout to the sites that have been defined for the import environment. Specifically, if a page layout is associated with a site that has a production URL that matches the production URL of a site defined on the import environment, then Commerce Cloud creates an association between the layout and the matching site. Note that, in order for this process to work, you must create the sites on the import environment before performing the import.

If no match is found, a warning message is provided during the import process. If a page layout does not have any site associations, it will be associated with all sites in the import environment.