JSON (Document Type)


images/download/thumbnails/44944809/arrow_up-version-1-modificationdate-1582773444161-api-v2.png Introduction: You can find a description of this phase in section Phase 2 (Introduction). See especially subsection When Does the Parser Start a New Record?


images/download/thumbnails/44944809/image2020-3-18_14-52-29-version-1-modificationdate-1584496348345-api-v2.png

This document type is used together with the Input Agent DataCockpit/Portal, but can also be used independently.


images/download/attachments/44944809/604-version-1-modificationdate-1649395197454-api-v2.png


(1) If this checkbox is set, the input fields are checked against their format templates during parsing. If a value violates the format template of the field or exceeds the field length, an error is created. If an error occurs, the profile job will not be aborted immediately in phase 2, but at the end of phase 2 or after 50 errors. Attention: The use of format checking puts a strain on performance and should only be used if absolutely necessary.

(2) Specifies whether to check the number of repetitions (of fields and nodes) in the source structure.

(3) Indicates whether the data should be summarised in a single record. Setting this checkbox prevents the parser from creating multiple records.

(4) Incoming files can be checked with semantic rules. See section Semantic Check .

Structure Templates


See section Templates for source and target structures.

Creating JSON Output Files


If you want to generate a JSON output file, have a look at the sections JsonCreationUnit , ExtendedJsonCreationUnit and Integration Units.