JSON Schema Importer

Select a Resource File containing your JSON schema definition.

• The importer reads this file to determine the properties, types, and structure to generate in your data model.
• To use, add your JSON Schema file as a Resource File in your Grooper project, then select it here.
• If the schema references other files, ensure those are also added as Resource Files in the same project folder.

Impact

The selected schema defines the hierarchy and data elements that will be created in your Data Model.
Changing the schema file and re-running the importer updates your data model to match the new structure.

A combination of the following flags:

This property is only used when the naming method for data elements is set to 'Cased'.

• Choose the desired casing style for generated names, such as PascalCase, camelCase, or UPPERCASE.
• Ensures consistency with your organization's naming conventions and improves readability in the data model.

Example

If set to PascalCase, a property named invoice_number in the schema will become InvoiceNumber in the data model.

For fields that can have multiple values (such as arrays), specify the character or string to use as a delimiter between values.

• The default is a comma (,).
• Example: If a field can have multiple phone numbers and the delimiter is ;, the value might be 555-1234;555-5678.
• Choose a delimiter that does not appear in your data values to avoid parsing errors.

Usage

Setting the delimiter enables array support for fields, allowing multiple values to be stored and processed as a single field.

When enabled, arrays of objects in the schema are imported as Data Tables when possible, rather than as multi-instance sections.

• Use this option to create tabular structures for repeating data, such as line items or lists.
• If disabled, repeating objects are imported as sections with multiple instances.

Considerations

Tables are only generated when the array items are objects with simple properties (not nested objects or arrays).

When enabled, Grooper-specific metadata and extensions (such as computed values, required conditions, and value delimiters) are imported from schemas produced by Grooper.

• Use this option to preserve advanced field settings and behaviors defined in Grooper-generated schemas.
• If disabled, only standard JSON schema properties are imported.

Extended properties include:

• x-computedValue: A formula for calculating the field's value.
• x-isValidIf: A condition that determines whether the field is valid.
• x-readOnly: A flag indicating whether the field is read-only.
• x-valueDelimiter: A custom delimiter for multi-value fields.
• x-typeName: A custom type name that maps to a specific Grooper Storage Type.
• x-expectedValue: A value that the field is expected to have, which can be used for validation.
• x-isRequiredIf: A condition that determines whether the field is required.