The services provided by the add-on allow you to export data from your EBX® repository. The source of the export is determined by the location from which you initiate the service. For example, running the export service from a table’s Actions menu sets that table as the source. Running it from a dataset’s Actions menu sets all tables within the dataset as sources.
When exporting at the table level, the export respects the view that is active at the time the service is initiated. An EBX® view defines which fields (columns) are visible to the user. Only the fields displayed in the selected view are included in the exported file. This behavior does not apply to dataset-level exports, which include all fields.
Overall, steps to export from a table or dataset are the same, except some details such as mapping differ. As outlined below, the export process includes:
Specifying the source file name and any format-specific options for CSV and Excel export, or selecting the desired target location when exporting SQL. See Exporting a table for instructions. Exporting to SQL is supported at the table level only and requires administrative configuration.
Defining any required mappings or transformations. The add-on automatically generates a map of all source fields to target fields. If your circumstances require it, use the add-on's drag-n-drop functionality to update the mappings. If you want to apply transformations to your data, you can use built-in functions to modify data during export. For more information on the topics of mapping and transformations, see Map and transform overview.
Saving settings as a template. When export operations require the use of transformations or custom mappings, you can use templates to store these settings. This alleviates you from having to redo the same tasks each time you perform a specific export.