Overview
In legacy Construct, pages could have a Download View Type that provided built-in export functionality for grid data. This functionality allowed users to choose the file type, select which columns to include, specify their data types in the export, and configure other options.
Construct Preview does not have a built-in download view type, but you can implement export functionality through using the capabilities of Replicate and Orchestrate module, and use toolbar buttons to run a custom orchestrate workflow to export a file in a dedicated drive in Syniti Drive.
Updated Methodology
Prerequisites
Create a dedicated drive or folder in Syniti Drive and a workspace in Replicate Preview. Refer to Syniti Drive and Creating a Workspace for more information.
Ensure that users of the construct page has access to that dedicated drive.
Create File Export Replication
Use a file export replication in Replicate Preview to export the grid container's existing dataset.
In Replicate Preview, access or create the dedicated workspace and create a target datastore of Syniti Drive type and select the required drive.
Create a source datastore of SKP Catalog type using the datastore details of the construct page associated with the grid container’s dataset.
Create a new file export replication using the dataset (table or view) that corresponds to the grid container.
Note
Use Field Mappings to define which columns need to be present in the export file.
This replication exports the file to the configured file path (export folder) in Syniti Drive.
Create an Export Workflow in Orchestrate
In Orchestrate, create an Orchestrate workflow using the Run Replication (Preview) task and selecting the above-mentioned file export replication. Refer to Run Replication (Preview) for more information.
Create a Toolbar Button Event
In the WebApp Builder, access the associated grid container and create a toolbar button with an event containing the orchestrate workflow as its task.
Users can use this toolbar button to run the orchestrate workflow which executes the file export replication.
Repeat the above steps to export data from each construct page’s container.
Note
If the container’s dataset has no existing records, the exported file still contains the column header row.
Translations must exist in Cloud Construct prior to running the export for column headers to appear in the translated language. If no translation exists, the technical column name is used in the header row.