Review export mappings, target clearing, filters, and scripts
Introduction
An Export defines a flow from an AnalyticsCreator object to an external target. Its field mapping connects source fields to destination fields. Use this how-to to review an existing export, decide whether to clear its target, restrict source rows when needed, and review field statements, variables, and scripts before saving.
The intended outcome is a saved export definition that matches your mapping and processing requirements. Saving the definition does not run the export or verify the destination data.
Screenshot examples: names, values, and checkbox states illustrate the interface. Use the objects and settings required by your own Data Warehouse (DWH) project. The pictured calendar-to-categories relationship is not a completed, compatible mapping to reproduce.
Applicability
Use these steps to maintain an existing export through Packages → Export in the AnalyticsCreator desktop interface. The source object, target Connector, destination structure, and export package must already be established. To create an export definition first, see Create an export definition with Export Wizard.
This workflow ends with saving and reopening the definition. Package execution and verification of transferred rows are separate tasks.
Prerequisites
3.1. An open Data Warehouse (DWH) project in which you can edit the intended export.
3.2. An existing export with a known source object, export package, target Connector, and destination object. The Connector defines the connection through which the target is accessed.
3.3. A field-by-field mapping plan identifying the source fields, destination fields, and compatible data types and lengths.
3.4. A decision about whether to retain or clear existing target rows and whether to export all source rows or a defined subset.
3.5. If the export requires a field statement, filter, variable, or script, its complete reviewed configuration, including field names, variable types and values, and script purpose. Expressions and statements must be suitable for the export's actual execution context.
Steps
Expand Packages
In the navigation tree of the intended Data Warehouse (DWH) project, expand Packages.
Locate the export package
Expand Export, then expand the package containing the export you need to review. An export package groups export definitions; identify it by the package assigned to your export, rather than its position in the tree.
Open the export
Right-click the required export item beneath its package, then click Edit export in the context menu.
Confirm the export and review field mappings
In the export editor, check the source-to-target relationship displayed in Export and the selected Package against your mapping plan. The Export relationship is read-only. If it identifies a different source or destination, return to the tree and open the intended item before editing.
Select Main. The Fields grid contains field mappings; the Variables grid beside it contains package variables. In Fields, select each row required by your mapping plan and enter the intended destination column name in Target Name if the mapping needs to change. Check the source field and destination field together, including their meaning, data type, and length.
- Source Name / Target Name — Source Name identifies the field supplying the value; Target Name identifies the destination field that receives it. The names may differ, but the fields must be compatible with the intended mapping.
- SSIS Statement — A field-level package statement for SQL Server Integration Services (SSIS). If the mapping requires a statement, enter the complete reviewed statement in this column. Leave it blank for a field that does not require one. Do not assume that a database SQL statement uses the same syntax.
Review all required mappings, including rows below the visible part of the grid. A blank Target Name in the screenshot is not an example of a completed mapping.
Decide whether to clear the target
If existing destination rows must be removed before the export writes data, select Truncate target. Inspect the complete Truncate statement and confirm that it names the intended destination. If the statement needs to change, enter the reviewed target-clearing statement for that destination.
If the export must retain existing target rows, clear Truncate target. Also check any export scripts for statements that would remove those rows; clearing this checkbox does not establish what a separately configured script does.
- Truncate target — Determines whether target clearing is part of the export. Select it only when clearing is required for your task.
- Truncate statement — The statement used to clear the target. Verify both the destination identity and the effect of the complete statement before saving.
Target-clearing example: the next capture shows TRUNCATE TABLE "dbo"."Categories". When executed, that statement clears the example Categories table. A source Filter does not restrict this statement to matching target rows. Do not copy the example table name into your export unless it is your intended destination.
Set the source-row filter
If the export should include only a subset of its source data, enter the complete reviewed condition in Filter. A filter restricts the source rows selected for export. Check each referenced field, comparison value, and expression against the actual source and intended row selection.
If the export should include all source rows, leave Filter empty or clear an existing condition after confirming that its restriction is no longer required.
Filter example: [IsActive] = 1 expresses a selection of rows whose IsActive value equals 1. Use this example only if your source has a suitable IsActive field and that condition matches the task. The pictured calendar mapping does not establish that this field is available or that the example has been tested for that export.
Expected Results: Filter contains the required condition, or is empty for an unfiltered export. Entering the condition does not retrieve or transfer rows.
Review package variables
On Main, compare the Variables rows with the variables required by your export statements. For each required variable, check the following columns against its reviewed configuration:
- Variable — The variable name.
- Type — Its data type.
- Description — A note explaining its purpose.
- Expression — Its assigned expression, when required.
- Initial value — Its starting value.
Correct values that differ from the intended configuration. Check that variable references in field statements correspond to the required variables. If the export needs no variables and the grid is empty, leave it empty. Review existing variable usage before removing or changing a row.
Review pre-export and post-export scripts
Select Scripts. Review existing script content against the work required before and after the export. For script changes, use the Original view of the relevant statement area:
- PreScript — Enter the reviewed SQL required before the export.
- PostScript — Enter the reviewed SQL required after the export.
Check the complete statements, referenced objects, and intended effects. Leave unused script areas empty. Review existing content before clearing it, especially where it prepares or changes target data.
Save the reviewed export
Review the source-to-target relationship, Package, field mappings, Truncate target, Truncate statement, Filter, variables, and scripts against the planned changes. Confirm that every required field has its intended mapping and that examples have not been substituted for real object names or expressions.
Click Save at the bottom of the export editor. If a validation error appears, read it, correct the identified configuration, and save again. Continue with Expected Results to check the saved definition.
Expected Results
5.1. Reopen the same item through Packages → Export → the intended package, right-click the export item, and click Edit export. Confirm the Export relationship and Package.
5.2. Compare the saved Fields mappings, field statements, target-clearing settings, Filter, and Variables on Main with your planned configuration. Select Scripts and compare both script areas with the intended statements. Required values should remain as saved, and unused settings should remain empty or cleared as intended.
5.3. The result of this task is a reviewed, saved definition. Data transfer remains unverified until the export is run and its destination rows are checked. Before accepting a later run, compare actual field values, row selection, target retention or clearing, and script effects with the export's intended outcome.
Decisions and variations
6.1 Retain or clear target rows. Use Decide whether to clear the target to set Truncate target. A filter on source rows does not turn a full-table truncate statement into a selective deletion.
6.2 Export all rows or a subset. Use an empty Filter for an unfiltered export, or a condition matching the required source rows as described in Set the source-row filter.
6.3 Use field statements, variables, and scripts when required. Review a field statement where the mapping requires it, its referenced variables in Review package variables, and before-export or after-export SQL in Review pre-export and post-export scripts. An export does not need example expressions or scripts merely because those areas are available.
Troubleshooting
- Object not found — Check the current Data Warehouse (DWH) project and expand the intended package under Packages → Export. Confirm which package owns the export. If the definition has not been created, follow Create an export definition with Export Wizard before returning to this task.
- Configuration differs after reopening — Confirm that you reopened the same export and package. Compare the saved values with the planned changes, correct any reported save error, and repeat Save the reviewed export and the checks in Expected Results. A closed editor alone does not verify the saved configuration.
- Runtime result differs — Compare the saved mappings and Filter with the actual source fields and rows. For unexpected target clearing, inspect Truncate target, the full Truncate statement, and scripts that change destination data. Saving the definition alone does not test these effects; verify them against the actual export run before accepting its result.