Data Export

Choose the Data Connection that defines the destination database server, authentication, and connection settings.

• The selected connection determines where all table mappings and custom statements will be executed.
• Only connections of type Data Connection are available for selection.
• If the connection is not set, export will not be performed.

Example

• Select a connection to an MS SQL Server, Oracle, or other supported database.

> [!TIP] > Configure your Data Connection in the repository before assigning it here.

Add one or more table mappings to specify how data from the document's Data Model is exported to database tables.

• Each mapping defines the target table, the columns to populate, and the corresponding data elements.
• Multiple mappings can be used to export to several tables (e.g., header and line items).
• Table mappings are executed in the order listed.

Example

• Map invoice header fields to an "Invoices" table and line items to an "InvoiceItems" table.

> [!NOTE] > At least one table mapping or custom statement must be defined for export to occur.

Add custom statements to perform advanced SQL operations, such as updating related tables, logging, or calling stored procedures.

• Statements can use data from the document's Data Model via expressions.
• Statements are executed after all table mappings.
• Use for scenarios not covered by standard table mappings.

Example

• Insert a log entry after export, or update a status flag in a related table.

> [!TIP] > Use custom statements for flexibility beyond standard data export.

Use this property to dynamically select a different database at runtime, based on document data or other criteria.

• Only supported for MS SQL Data Connections.
• The alternate database must have the same schema as the primary database.
• The expression can reference fields from the document's Data Model.

Example

• Route exports to a customer-specific database by evaluating a field such as "CustomerId".

> [!NOTE] > If set, the connection must be an MS SQL Data Connection. Leave blank to use the default database.

The 'Link Name' property determines the label assigned to the Content Link created during export.

• This name is used to identify the exported content link on the Batch Folder or document.
• If not set, a default value such as "Export" is typically used.
• You can use different link names to distinguish between multiple export destinations or export runs.
• The link name appears in the Grooper UI and can be referenced in downstream activities or scripts.

Example:

• Set 'Link Name' to "CMIS Export" to clearly indicate that the link references a CMIS Repository export.
• Use different names like "Archive Export" or "Cloud Export" if exporting to multiple systems.

<em>Tip: Use a descriptive link name to make it easier for users and automation to identify the correct exported content, especially when multiple links are present on a Batch Folder.</em>