Tailoring Overlay

Extend an existing core-library Datex Studio component (most commonly a grid, but the model applies analogously to forms, editors, and hubs) via the baseConfiguration overlay mechanism, or flatten a tailored overlay into a standalone custom_<base> variant. A tailored component references a base via baseConfiguration, inherits its full contract, and layers targeted overrides on top — new columns, new flows, customization hooks against existing flows, additional secondary datasources, suppressed items. The overlay tracks the base as it evolves; flattening collapses the overlay into a fully authoritative copy when the customer's needs have diverged enough that the inheritance no longer pays for itself.

References

• ../datex-studio-shared/branch-setup.md — Branch/connection selection (shared across skills)
• references/tailoring.md — Authoritative tailoring reference: provenance variants, anatomy of a tailored component (baseConfiguration, fromBaseConfiguration: true shadow marker, onCustomization<Slot>FlowConfig hook pairs, removed: true suppression), secondary enrichment datasources, the 12-step flatten-to-custom recipe, pre-flight checklist
• ../datex-studio-conventions/file-format.md — configurationTypeId table and TypeScript-expression encoding rules (tailoring is not its own type — the type identifier is whatever the tailored component is, most commonly grid)
• ../datex-studio-conventions/naming-conventions.md — tailored_ / custom_ prefix rules; tailored_<base>_grid naming
• ../datex-studio-runtime/runtime-globals.md — platform-injected globals available in tailored flow code ($grid, $row, $flows, $apis, $utils, ...) — identical to the base's tier
• ../grid-creator/references/grids.md — grid authoring reference (the most common tailored component type) — five-location rule, imperative cell API, embedded datasource envelope
• ../datasource-creator/references/flow-datasources.md — flow-type datasource shape for tailored secondary (tailored_ds_<base>) enrichment datasources
• ../datasource-creator/references/odata-datasources.md — schema pre-flight applies when flattening to a custom that newly authorizes OData fields
• ../component-wiring-check/references/component-wiring.md — vars-must-be-declared rule applies to tailored flow code and to flattened custom flows

Dependencies