Import properties

Instead of adding every property by hand, you can let DASH build them for you from a sample file. Import a CSV to create one property per column, or an XML structure file to reproduce a nested hierarchy of entity and value properties. The import runs as a background job, so a large file won’t hold up the page.

Before you start

• You need the Definitions update permission. See Roles & permissions.
• Import into an empty definition. An XML-structure import is refused if the definition already has properties: “Definition already has properties. Create a new definition or clear existing properties first.”
• Import is refused once the definition is referenced by a certificate: “Cannot import to definition with existing submissions.”

What each import type produces

• CSV import — DASH reads the file’s columns and creates one property per column.
• XML-structure import — DASH parses the document into a nested hierarchy of entity and value properties, so structured output is reproduced automatically.

Import from a sample file

1. Open the definition (it must have no properties yet) and stay on the Definition Details tab.
2. Drag your file onto the upload area, or select it to browse. The area prompts you to “Upload an example XML file from your customer and we’ll auto-detect the definition structure.”
3. DASH starts the import in the background. While it runs you’ll see a status such as “Importing XML structure…” with the note “Parsing your file and building the definition. This may take a few seconds.”
4. When the job finishes, the generated properties appear in the list. Review them and adjust names, types and units as needed — see Add & manage properties.

Uploading a sample file to auto-detect definition structure

One import at a time, and the right file type

• Only one import can run per definition at once. Starting a second is refused: “An import is already in progress for this definition.”
• The file must match the import type. A CSV import rejects a non-CSV with “File must be a CSV file.” and an XML-structure import rejects a non-XML with “File must be an XML file.”
• If a job fails, the definition reports the failure with an error message — fix the file and try again.

Related

• Add & manage properties
• Create a definition
• Definitions overview
• Locking & archiving
• CSV & Excel mapping