Schemas & Layouts
Schemas and layouts define the structure of your data so that Adeptia knows what fields are available, how they are organized, and how they relate to one another. By describing your data's shape up front, you give the platform everything it needs to map fields, transform records, and move information accurately between systems.
What schemas and layouts do
A schema is a reusable description of a data format. It captures the fields, their types, whether they repeat, whether they are required, and how they nest inside one another.
Supported data formats
Adeptia supports schemas for a broad range of data formats, so you can integrate structured, semi-structured, and industry-specific data in a single platform.
| Format category | Formats |
|---|---|
| Structured / tabular | Database, advanced database, Excel, text (delimited), advanced text, positional text |
| Hierarchical | JSON, XML |
| Industry standard | EDI |
How schemas fit into an integration
Schemas sit at the center of the mapping step in any integration. Adeptia uses the field trees defined in your schemas to understand the structure of the data being processed.
What you provide when defining a schema
The information you supply depends on the format you are working with. Each format has its own structural details:
| Format | What you describe |
|---|---|
| JSON | The field hierarchy and how arrays are handled |
| XML | The element and attribute tree, including any namespaces |
| EDI | The transaction standard and whether HIPAA rules apply |
| Excel | Which sheet to read and where data rows begin |
| Text / positional | How fields and records are separated |
| Database / advanced database | The table, schema, and catalog associated with the data |
Field-level detail available for mapping
Each field in a layout carries metadata that Adeptia uses during mapping and transformation. This includes the field's data type, whether it can repeat (appear multiple times in a record), whether it is required, any default value, and documentation notes. For XML-backed schemas, namespace information is preserved at the individual field level so that source paths remain accurate even when a document mixes multiple namespaces.
Searching and reusing schemas
You can retrieve schemas by format type or search by name. This makes it easy to find an existing schema before creating a new one, encouraging reuse and keeping your integration assets consistent.