--- title: "Adding File Export Replications" slug: "adding-file-export-replications" updated: 2026-11-16T14:33:41Z published: 2026-11-16T14:33:41Z canonical: "skthelp.syniti.com/adding-file-export-replications" --- > ## Documentation Index > Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt > Use this file to discover all available pages before exploring further. # Adding File Export Replications You can export data to a file in Syniti Drive by using it as the target datastore, with an SKP Catalog System as the source datastore. You can bulk create file export replications using the [Source Table Selection](/v1/docs/configure-workspace-datastores#selecting-source-tables) feature or create manually. To manually create file export replications: 1. In the Targets panel, select the required Syniti Drive as the target datastore. 2. In the Sources panel, select the required SKP Catalog System as the source datastore. 3. In the Replications panel, click the **Add Replication** (**+**) button. The New Replication dialog box is displayed. 4. In the Source section, complete the following steps: 1. Select the required table you want to export. 2. If required, you can filter out records from this table using the Source Filter field. > [!NOTE] > **Note** If this replication will be included in an Orchestrate workflow of custom type, you can enter variable placeholders `{{VariableName}}` within the Source Filter field to update replication source filters dynamically. 5. In the Target section, complete the following steps: 1. From the Export As list, select the required file format. > [!NOTE] > Note > > When you select an export format, format-specific options appear, allowing you to customize the export settings. 2. In the Delimiter field, specify the character that separates values in the file. Default character is comma (,). For example, enter comma (,) or pipe (|) if you are exporting data in .txt format. 3. From the Encoding list, select the required text encoding to be used in the file to ensure special characters are read properly. The default encoding format is UTF-8. 4. From the Text Qualifier list, select the character to delimit string values. The default text qualifier is double quotes ("text"). 5. To exclude column headers when exporting a table, turn off the Include Headers toggle. By default, this toggle is enabled. 6. **For **XML Export** replications, enter the following details:** | Field | Description | | --- | --- | | Root Tag | The top-level wrapper element that contains all exported records. The default value is `Root`. You can also specify a domain-specific name that reflects your data. | | Row Contains XML Data | Determines how {{variable.Replicate Preview}} processes each row of data. - **Turn off** this toggle if you're exporting normal database columns (recommended for most cases). This converts each column into an XML element for each record. - **Turn on** this toggle only if a single source column already contains formatted XML data that you want to preserve as-is. | | XML XSI Label | The XML Schema Instance namespace declaration to include in the XML export. The default value is `http://www.w3.org/2001/XMLSchema-instance`. | | XML Namespace (ns1) | Qualifies elements with a custom namespace prefix. Use only if integrating with systems that require specific namespace prefixes. Leave blank for standard exports. | | XML Namespace (ns2) | Adds a second custom namespace for complex documents. Use only when your XML document uses multiple data vocabularies. | | XML Schema Location | The location of your XML Schema file (URL, file path, or relative path). This value will be included as the `xsi:schemaLocation` attribute in the exported XML. Leave empty if not applicable. | 7. To modify the file name, update the Target Name field. 6. (Optional) In the Additional Properties section, complete the following steps: 1. To specify higher preference for this replication over others, enter a priority value in the Priority field. Note The replications will be ordered and executed using the Priority value. By default, the value for each replication is set at 1000, which provides equal preferences for all replications, but ordered using the creation time of a replication. 2. Select **Pre-Execution** and **Post-Execution Workflows** to run if this replication is integrated with other module’s tasks in an Orchestrate workflow. 7. Click **Save**.