Browse every site archive XML file of your project by organization and site, search them, and open IDs from scripts in the site archive XML
B2C Metadata lists the site archive XML files of your project in one tool window: metadata, catalogs, price books, libraries, preferences, jobs, services, slots and the other import files. Each file sits under the organization or the site it belongs to, with its size and its archive
The organization's data at the top of the site archives: metadata, catalogs, price books, shared libraries, jobs, services, global preferencesEach site's data, under sites/<site> in the site archives or in an export folder named for the site: preferences, content slots, promotions, customer groupsSite data in no sites/<site> folder and in no folder named for a siteCatalogs: http://www.demandware.com/xml/impex/catalog/2006-10-31List the kinds of files, each with its sites, instead of Organization and SitesLook for site archive XML againhttp://www.demandware.com/xml/impex/services/2014-09-26Down
B2C Metadata lists every site archive XML file of the project under Organization and Sites, with its size and archive. Narrow it to one site, list the kinds first with Group by Type, search by name, kind or path and open a file with Enter, copy its path or namespace, and find the same tree under META in the B2C project view
The organization's data at the top of the site archives: metadata, catalogs, price books, shared libraries, jobs, services, global preferencesEach site's data, under sites/<site> in the site archives or in an export folder named for the site: preferences, content slots, promotions, customer groupsSite data in no sites/<site> folder and in no folder named for a siteCatalogs: http://www.demandware.com/xml/impex/catalog/2006-10-31List the kinds of files, each with its sites, instead of Organization and SitesLook for site archive XML againhttp://www.demandware.com/xml/impex/services/2014-09-26Down
B2C Metadata lists every site archive XML file of the project under Organization and Sites, with its size and archive. Narrow it to one site, list the kinds first with Group by Type, search by name, kind or path and open a file with Enter, copy its path or namespace, and find the same tree under META in the B2C project view
Click B2C Metadata on the right tool window bar, after B2C Entry Points. You can also open it from:
The menu items show up once a cartridge is linked and focus the search field. The window looks for files while it opens, so it first reads Looking for site archive XML...
The organization's data at the top of the site archives: metadata, catalogs, price books, shared libraries, jobs, services, global preferencesEach site's data, under sites/<site> in the site archives or in an export folder named for the site: preferences, content slots, promotions, customer groupsSite data in no sites/<site> folder and in no folder named for a siteCatalogs: http://www.demandware.com/xml/impex/catalog/2006-10-31List the kinds of files, each with its sites, instead of Organization and SitesLook for site archive XML againhttp://www.demandware.com/xml/impex/services/2014-09-26Down
B2C Metadata lists every site archive XML file of the project under Organization and Sites, with its size and archive. Narrow it to one site, list the kinds first with Group by Type, search by name, kind or path and open a file with Enter, copy its path or namespace, and find the same tree under META in the B2C project view
Control
What it does
Search
Search metadata, catalogs, preferences, jobs, services filters the tree
Scope
All, Organization, All Sites, or one site under Sites. The project keeps your choice
Group by Type
Lists the kinds of files first, each with its sites
Refresh
Looks for site archive XML again
Expand All, Collapse All
The tree's branches
The footer counts what you see: 9 files in 2 archives, 2 of 9 files while a scope narrows the tree, or 2 matches while you search
The organization's data at the top of the site archives: metadata, catalogs, price books, shared libraries, jobs, services, global preferencesEach site's data, under sites/<site> in the site archives or in an export folder named for the site: preferences, content slots, promotions, customer groupsSite data in no sites/<site> folder and in no folder named for a siteCatalogs: http://www.demandware.com/xml/impex/catalog/2006-10-31List the kinds of files, each with its sites, instead of Organization and SitesLook for site archive XML againhttp://www.demandware.com/xml/impex/services/2014-09-26Down
B2C Metadata lists every site archive XML file of the project under Organization and Sites, with its size and archive. Narrow it to one site, list the kinds first with Group by Type, search by name, kind or path and open a file with Enter, copy its path or namespace, and find the same tree under META in the B2C project view
Organization holds the data at the top of the site archives: metadata, catalogs, price books, shared libraries, jobs, services and global preferences. Sites holds each site's data: preferences, content slots, promotions and customer groups. Each file row shows its name, its size and its archive in grey. The size is coloured from green for the project's smallest files to red for its largest. Hover a group or a file for what it holds
The plugin decides the owner from the file, so exports that don't follow the archive layout still land in the right place:
File
Belongs to
Anything under sites/<site>/
That site
A site file in an export folder named for a site, such as SoloUS/preferences.xml or us/jobs.xml
That site
A custom object
The storage-scope of its type in your metadata, site or organization
A library under libraries/<id> or with a library-id
The organization, as a shared library
Preferences outside a site folder
Site or organization, from the preference IDs it sets
Group by Type lists the kinds instead, such as Metadata, Custom Objects or Preferences, each with its sites and then its organization files. The setting is shared with the META node of the B2C project view
The organization's data at the top of the site archives: metadata, catalogs, price books, shared libraries, jobs, services, global preferencesEach site's data, under sites/<site> in the site archives or in an export folder named for the site: preferences, content slots, promotions, customer groupsSite data in no sites/<site> folder and in no folder named for a siteCatalogs: http://www.demandware.com/xml/impex/catalog/2006-10-31List the kinds of files, each with its sites, instead of Organization and SitesLook for site archive XML againhttp://www.demandware.com/xml/impex/services/2014-09-26Down
B2C Metadata lists every site archive XML file of the project under Organization and Sites, with its size and archive. Narrow it to one site, list the kinds first with Group by Type, search by name, kind or path and open a file with Enter, copy its path or namespace, and find the same tree under META in the B2C project view
Type a file name, a kind or a path: objecttype finds both metadata files, and catalog finds the catalogs. Names match as in Search Everywhere, and the matched part is highlighted
The organization's data at the top of the site archives: metadata, catalogs, price books, shared libraries, jobs, services, global preferencesEach site's data, under sites/<site> in the site archives or in an export folder named for the site: preferences, content slots, promotions, customer groupsSite data in no sites/<site> folder and in no folder named for a siteCatalogs: http://www.demandware.com/xml/impex/catalog/2006-10-31List the kinds of files, each with its sites, instead of Organization and SitesLook for site archive XML againhttp://www.demandware.com/xml/impex/services/2014-09-26Down
B2C Metadata lists every site archive XML file of the project under Organization and Sites, with its size and archive. Narrow it to one site, list the kinds first with Group by Type, search by name, kind or path and open a file with Enter, copy its path or namespace, and find the same tree under META in the B2C project view
Down selects the first file and moves to the tree
Enter in the search opens the first file
Typing in the tree goes back to the search
The tree shows up to 500 files, then N more, refine the search
A search with no file reads Nothing matches "promo", and a scope with none No files in SoloUS
The organization's data at the top of the site archives: metadata, catalogs, price books, shared libraries, jobs, services, global preferencesEach site's data, under sites/<site> in the site archives or in an export folder named for the site: preferences, content slots, promotions, customer groupsSite data in no sites/<site> folder and in no folder named for a siteCatalogs: http://www.demandware.com/xml/impex/catalog/2006-10-31List the kinds of files, each with its sites, instead of Organization and SitesLook for site archive XML againhttp://www.demandware.com/xml/impex/services/2014-09-26Down
B2C Metadata lists every site archive XML file of the project under Organization and Sites, with its size and archive. Narrow it to one site, list the kinds first with Group by Type, search by name, kind or path and open a file with Enter, copy its path or namespace, and find the same tree under META in the B2C project view
Double-click a file or press Enter to open it. Metadata files open in the Metadata Editor, and services, jobs, preferences, custom objects, slots and libraries in their site archive editor. Right-click a file for:
Item
Does
Open
Opens the file
Open Schema (services.xsd)
Opens the bundled schema of the kind, when it has one
Reveal in Project View
Selects the file in the Project tool window
Copy Path
The full path
Copy Path from Content Root
The path inside the project, such as metadata/site_us/services.xml
The B2C project view shows the same files under META, beside the site's root, where External Libraries sits. It has the same groups, counts and sizes, follows Group by Type, and selects the file you open, such as META › Sites › SoloUS › Preferences › preferences.xml. META shows up with the first site archive file
The organization's data at the top of the site archives: metadata, catalogs, price books, shared libraries, jobs, services, global preferencesEach site's data, under sites/<site> in the site archives or in an export folder named for the site: preferences, content slots, promotions, customer groupsSite data in no sites/<site> folder and in no folder named for a siteCatalogs: http://www.demandware.com/xml/impex/catalog/2006-10-31List the kinds of files, each with its sites, instead of Organization and SitesLook for site archive XML againhttp://www.demandware.com/xml/impex/services/2014-09-26Down
B2C Metadata lists every site archive XML file of the project under Organization and Sites, with its size and archive. Narrow it to one site, list the kinds first with Group by Type, search by name, kind or path and open a file with Enter, copy its path or namespace, and find the same tree under META in the B2C project view
Right-click a folder and choose New › Site Archive File for an empty file that imports without errors:
Kind
File
Root
Services
services.xml
services
Jobs
jobs.xml
jobs
Site preferences
preferences.xml
preferences
Custom objects
custom-objects.xml
custom-objects
Content slots
slots.xml
slot-configurations
Content library
library.xml
library
The folder puts its kind first: sites/RefArch offers preferences, libraries/SharedLibrary a library with library-id="SharedLibrary", custom-objects custom objects. The other kinds stay in the list. For metadata, use New › Metadata File, see Metadata Editor
The Site Archive tab of Search Everywhere finds what the files define: services, profiles and credentials, jobs, preferences, custom objects, slot configurations, and library contents and folders. Enter opens the file in its editor with that row selected
Service, credential, preference and custom object IDs in scripts link to the XML that defines them. Cmd+Click / Ctrl+Click opens the definition, and completion lists the IDs of the project with where each one comes from
The window doesn't build an XML tree. It reads each file up to its root element, so a catalog of hundreds of megabytes costs what a small file does, and it keeps what it read across restarts. Folders named cartridge and node_modules, and dot folders, are skipped. A change to a file updates the tree within a moment, unsaved edits included