Dawiso allows you to easily import and export objects and their attributes to support:
- Data backup: Exporting data allows you to create backups, ensuring that critical information is protected and can be restored in case of loss or corruption.
- Data migration: When transitioning to new systems or updating existing ones, data export and import facilitate the smooth transfer of objects and attributes, preserving continuity.
- Record organization: Exporting data to external files helps organize and review large volumes of information offline, providing flexibility for data management or compliance reporting.
Dawiso currently supports:
- The import of Excel (.xlsx) files.
- The export of Excel (.xlsx), Word (.docx), and PDF files.
To enable import and export, configure it in the settings section of your package.
Ensure your data does not exceed Excel’s hard limits, such as 32,767 characters per cell (including HTML). Data over this limit is trimmed, which may result in missing information.
Exporting objects in Excel
- In Dawiso, open your app and click the three dots on the left side navigation.
- From the list, select Export objects.
- Select Excel.
- Select Object to export (the Templates option is used for Object import (Excel)):
- Objects
- Object details
- Attributes
- Relations
- Select at least one object to export.
- [Optional] Select which attributes, relations (to other objects), user relations (ownership) to export.
- Click Export. Depending on your file size, you may need to wait for a few seconds.
- In the top-right of Dawiso, click the notification bell button. Look for the notification that says
Export of objects to file has finished: Click to downloadfor the download link.
To change the default date format of your Excel files, see the following articles:
Exporting objects in Word/PDF
- In Dawiso, open your app and click the three dots on the left side navigation.
- From the list, select Export objects.
- Select Word or PDF.
- Select a Word template configured for your application.
- [Optional] Enable one of the following options:
- Enable Generate multiple documents based on top-parent object to export each parent object with its children as a separate file.
- Enable Put all files in one folder to organize both attachments and exported objects in the same folder. Keep in mind that the exported information (especially the formatting) may differ in appearance from how it is displayed within Dawiso.
Tip
A PDF export is simply the PDF version of a Word export. Use packages to configure the highlight of changed and deleted text in Word and PDF exports.
- Select at least one object to export.
- [Optional] Select which attributes, relations (to other objects), user relations (ownership) to export.
- Click Export. Depending on your file size, you may need to wait for a few seconds.
- In the top-right of Dawiso, click the notification bell button. Look for the notification that says
Export of objects to file has finished: Click to downloadfor the download link.
Word exports will always include toggle lists for certain components, such as embedded diagrams. If no components are included, the toggle list will still be present but empty.
Export document versions between two dates
When enabled for an application, you can export all Word document versions that changed within a date range selected in the changelog. The output is a ZIP file with each version stored as a separate file.
To use this export, an administrator must enable it in the application settings. For more information, see settings (asset).
- Open an object, click the three dots in the object header and select Changes. Choose a change and click Show version.
- In the top-left, select two dates to define the time range.
- Click the three dots next to the object in the Explorer and select Export objects.
- Select Word and choose a template.
- The Export versions for the selected time range option is pre-checked. Review the time range and confirm.
- Select the objects to export and click Export.
- In the top-right of Dawiso, click the notification bell button and download the ZIP file when it is ready.
This export may take significantly longer than a standard Word export, as it generates a separate file for each version. It runs as a background task and does not block other exports. If no versions changed within the selected range, nothing is exported.
Word templates
Word templates ensure the uniformity of your object export to Word files.
On the Word Templates (Settings > Configuration > Word Templates) page, you can manage all your templates. To assign them to specific applications, refer to the Packages Documentation. At least one template must be assigned for Word and PDF exports to be enabled.
Add a Word template
- In the top-right corner, click the + New template button.
- Fill in the following fields:
- Name: Template name displayed on the Word Templates page and on the template selection window.
- Key: Reference key used in packages.
- Attachment: Word file attachment with the template.
- [Optional]** Description**: Description for better understanding of the purpose and use of the template. Displayed on the Word Templates page.
- Finish configuration by clicking Save.
Manage Word templates
Identify your template and click the three dots on the right. Here, you can:
- Edit your template: All fields except for the key can be changed.
- Download the template: Word file with the template as the contents.
- Delete the template
Create a Word template
Every Word template is composed of the following sections, which can be configured:
- Object detail section
- Multi object section
- Header and footer
The Word Export Template configuration section is aimed at more advanced users of Dawiso as you will be need to reference properties created in JSON packages.
Each section can contain components, for which the following rules apply:
- Components will be replaced with data from the database (the components function as merge fields or variables).
- Components must be in the
<<{jsonTemplate}>>format. - Any text within double angle brackets (
<< >>) must be formatted as JSON. - All components must have a
typefield, which specifies the component type. - Components in the object detail section can include display conditions.
Any static text and formatting of the template will stay consistent across exported objects.
Example of a basic Word template (change placeholder component types and attribute types to the ones used in your object type template):
<<Object details>>
<<{"type": "objectName", "useNumbering": true, "styles": ["1 Number Heading", "2 Number Heading", "3 Number Heading"]}>>
<<{"type" :"attribute", "attributeType": "definition", "style": "Normal" }>>
<<{"type": "text", "text": "Only when definition is not null", "style": "1 Number Heading", "conditions": [ { "type": "attribute", "value": "project_id", "operator": "not empty" } ] }>>
Status:
<<{"type": "objectProperty", "property": "Status", "style": "Normal"}>>
Přílohy:
<<{"type" :"attachments", "header": "Attachments", "headerStyle": "Attachments"}>>
<</Object details>>
For the full step-by-step guide, see Word Export Template.
Export Control
When Export Control is configured for an application, PDF and Word exports may include compliance annotations and additional access controls.
Compliance annotations
If the exported set contains at least one object with an active Export Control flag, PDF and Word exports receive:
- Page header: A classification text on every page.
- Inline annotation: A line below the chapter heading for each chapter whose own object directly carries the flag.
- Document metadata:
Export Control = Yesin document properties (fixed marker, not translated).
Annotation texts appear in the language of the user who triggered the export. Exports without flagged objects and all Excel exports are produced without annotations.
Microsoft Information Protection
Dawiso also supports Microsoft Information Protection (MIP), which allows exported Word documents to be encrypted and access-restricted using Microsoft sensitivity labels. When this functionality is enabled, Word exports that contain MIP-sensitive objects are automatically encrypted before delivery. The resulting file requires Microsoft 365 permissions to open.
Export Control is configured in packages. For more information, see settings (asset) and features (attribute type).