The active B2C Site Scope tells the extension which site's cartridge path to use. Choose the site you are working on so navigation and override resolution use its cartridge order, and endpoint actions open the corresponding storefront.
Select a site
Select your connection
Activate the intended sandbox connection in the Intellij SFCC sidebar. The selected scope belongs to that connection, so switching connections can also change the site context.
Open the B2C Scope selector
Click B2C Scope: [site] ([count]) in the VS Code status bar. Type a site ID to narrow the list. Global is the fallback when the active connection has no selected site.
Choose the source of the cartridge path
Select a site under Found in project site.xml files to use a local site export, or under Found on [connection] to use the path retrieved from the active instance. Press Enter to select it.
Check the selected order
Hover over the status bar item to see the site, cartridge count, and source. Use Open Cartridge Path for the numbered list or Copy Cartridge Path for its colon-separated value.
Local and remote sources
| Source | Where the scope comes from | How changes reach it |
|---|---|---|
Local site.xml | The file's site-id and <custom-cartridges> value. The picker shows the file location. | Saving changes to a selected local site file refreshes its site ID and cartridge order for connections using that file. |
| Remote instance | Sites and their cartridge paths retrieved through the active connection. | Reopen the selector to fetch the instance's sites and select the updated scope. |
The source matters even when the site IDs match. Selecting a local export lets you work with that export's order; it does not apply the order to the remote site. The Open source link in the status bar tooltip opens the local XML or Business Manager, depending on the selected source.
Why cartridge order matters
For a synthetic path such as:
app_demo_custom:app_storefront_baseapp_demo_custom has priority over app_storefront_base. When both contain the same cartridge-relative file, site-aware navigation can resolve the effective implementation and its override chain using that order. module.superModule navigation follows the next implementation in the chain.
The cartridge list marks names as Linked or Not linked. A remote path can reference a cartridge whose source is absent from the local project. Link the corresponding local cartridge before expecting navigation into its files.
Scope selection updates the extension's cartridge ordering and the context sent to the script and ISML language servers. Open Endpoint and Copy Endpoint URL also require a selected site and an active connection. Selecting a scope does not upload code or modify the site's settings.
Edit a local cartridge path
Open the selected local site.xml and use Edit [site ID] Cartridge Path ([count]) above <custom-cartridges>. The Cartridge Path Editor provides an ordered list with drag, add, and remove controls. Save the source XML to refresh the local scope.
Troubleshooting
- The status bar shows Global: select a site for the active connection. Global has no selected site's cartridge path.
- A local site is missing: confirm its file is named
site.xml, is valid XML, and has asite-idon the<site>element. Check the file location when multiple exports contain the same site ID. - A remote site is missing or cannot load: confirm the intended connection is active and can access that instance. Reopen the selector after resolving its connection error.
- Navigation resolves an unexpected cartridge: inspect the source and order in Open Cartridge Path, then confirm the expected cartridge is linked locally. A local export and the live site may have different paths.
- A saved edit has no effect on a remote scope: the selection still uses the instance's path. Select the local scope to use its XML for code assistance, or apply the site change remotely through your normal workflow and select the refreshed remote scope.
