Analyse file for structure

You can open the following dialogue via the source structure menu or the target structure menu.

Depending on the type of file, a specific dialogue will be opened in which further settings can be made. The uploaded file is then analysed and an appropriate source or target structure is automatically generated.

The following files can be analysed. These are the data files themselves, only XSD/DTD is a schema file. If you do not find your file format here, there are further possibilities on pages "Import structure" and "Main settings". See also section Working with templates in general.


  • JSON

  • CSV

  • Excel

  • XML

  • XSD/DTD Schema

  • X12

  • EDIFACT

  • IDoc

  • Swagger (JSON)

  • RESTful API ML (RAML)


In the following, we only deal with dialogues that have no self-explanatory settings or are not already linked to other sections.

JSON


Note: If the file contains arrays with several different data types, then the analysis works only partially and must be adjusted manually.


(1) JSON Lines Format: Setting this checkbox is only necessary if option "JSON Lines Format" is used in phase 2 (document type "JSON").

(2) JSON Lines Format, Chunk > 1: In addition, the chunk size must match, since a different structure is created for a chunk size >1 and parsing only works with the matching structure.

CSV


(3) Row(s): The row within the file that is to be used as an example for the structure to be created.

(4) CSV delimiter: The field delimiter.

Excel


(5) Record: The Excel sheet to be used.

(6) Row(s): The row within the file that is to be used as an example for the structure to be created.

XML


(7) XSD parser settings: These settings are identical with the ones in section XML schemas - XSD/DTD files.

(8) No complex fields: This option should always be activated if no repetition of the same field within a node can occur. Any XML element that has no sub-elements or attributes is then represented as a simple field in the structure. Otherwise, every simple field would be represented as a node containing a value field "<nodename>_val". See also section Match codes, unique/reserved names for XML.

RESTful API ML (RAML)


(9) Type to use: Here you have to specify the RAML resource type ("start" node) that you want to represent in your structure. Details about RAML can be found at www.raml.org.