Configuring a schema

At a glance

• Not every template has schema settings to configure — many skip straight to Entries.
• When there are settings, they're grouped into sections, with anything marked "Advanced" tucked into a collapsed panel.
• Required settings must be filled in before you can continue.

Some templates have schema-level settings that need to be filled in before you start mapping individual fields — things the schema itself needs to know, rather than something specific to one entry. If a template doesn't have any, you won't see this screen at all; setup takes you straight to Working with entries.

What you'll see

Settings are grouped into sections, each with a title and a short description of what it's for. A setting less commonly needed is grouped under an Advanced panel, collapsed by default — expand it if you need it, otherwise you can ignore it.

Some settings let you reference a value you've already declared elsewhere in the template (see Declaring variables with context) instead of typing a fixed value — when that's available for a setting, you'll see your declared variables offered as choices.

Continuing

The Continue button at the top stays disabled until every required setting has a value — optional ones can be left as their defaults. Once you continue, you land on Working with entries. You can come back and change these settings later using the Configure shortcut in the workspace's top bar.

Sections that reveal more sections

A section can depend on another section's setting — MorphMapper calls this a condition. The dependent section only renders once the setting it depends on has a particular value; until then it doesn't appear at all, not even disabled. The most common shape of this is a checkbox that unlocks a follow-up group when checked.

For example, an intermodal export template's Update Template Settings section starts with a single checkbox, Update Template ("Check if this is an update of an existing template."). Checking it reveals three more sections beneath it, all conditioned on that same checkbox:

Field	Type	Description	Default
Container Merging	Dropdown (Single / All Update)	Whether a single matching container or every matching container gets updated.	All Update
Container Fields	Multi-select	Which container fields to update (for this schema: export, container, invoicereference).	Empty
Skip Fields	Multi-select	Fields/items to leave untouched during the update.	Empty

Unchecking Update Template hides all three again — their values aren't cleared, just hidden, so re-checking it brings back whatever you'd set.

The choices offered by Container Fields and Skip Fields aren't drawn from your uploaded file — they're a fixed list baked into the schema definition itself, so they're the same regardless of what you import. Confirmed live on an intermodal Xml import template: Container Fields offers import and container; Skip Fields offers field 1 and field2. An export template's schema definition can list a different set of fields for the same settings.

Advanced settings

Some sections are always in the collapsed Advanced panel instead of the main list — not because they depend on another setting, but because the template author marked them as less commonly needed. On a PDF export template, for instance, PDF Settings (a single Separate Pages checkbox, for whether to process every page of the source PDF together rather than as separate documents) shows up under Advanced rather than inline, alongside Submission Settings.

Advanced options within a section

The Advanced panel above collapses whole sections. A section can also have individual options marked advanced, as a separate mechanic: each section splits its own options into a standard list and an advanced list, tucked into its own nested accordion titled "Advanced <section title>" underneath the standard ones. A section's own Advanced status and its options' Advanced status are independent — a non-advanced section can still have advanced options tucked into its inner accordion. Neither of the sample schemas used in this guide (the intermodal import/export schemas) marks an individual option advanced this way, so this can't be demoed against sample.xml. It's confirmed by reading the component's rendering logic instead.

Declared-variable choices

A setting whose input is one of your file's declared variables (see Declaring variables with context) shows a dropdown populated with the variable names you've defined, rather than a fixed list of choices — so what you see there depends entirely on what your template has declared. If nothing's been declared yet, that dropdown is empty.