Destinations

Setting up writeback destinations in Plan

Plan supports fast writeback setup and execution for several types of data destinations

• Database/ Data warehouses/ Data lake: Azure SQL, SQL Server, Synapse Analytics Dedicated SQL Pool, Azure Data Lake, Fabric lakehouse, Fabric warehouse, Dataverse, Databricks, Snowflake, BigQuery, Amazon Redshift, Oracle, SingleStore, PostgreSQL, MySQL,

• File Destinations: OneDrive, SharePoint

• Webhook URLs: Can be used to trigger workflows in iPaaS such as Power Automate and Logic Apps)

Configuring writeback destination(s) is straightforward and involves the same procedure (picture below) for any destination.

1. Click on Writeback > Add Destination

2. A list of destinations will be displayed for the users to select from.

Add writeback destination

Configuring destinations for writeback is a straightforward process that will be covered in the upcoming sections.

Generic destination settings

1. Client-managed and Plan-managed destination

After configuring the destination, you can choose whether the destination should be client-managed or Plan-managed. If you wish to restrict access to the database, opt for client-managed destinations.

• Enable automatic writeback management: For Plan-managed destinations, Plan will automatically create the writeback table. However, Plan needs to be provided with the required permissions on the table.

Plan managed destinations

• For client-managed destinations, Plan will generate the scripts. You can manually execute them against the database.

Client managed destination

2. Column config

• Decimal Precision

Plan rounds off all numeric values including percentages to a specified number of decimal points as per your configuration instructions. When you create the first connection, you can specify decimal precision for all connections in that report.

Plan supports a maximum precision of 10 digits.

Setting the decimal precision for destinations

When you apply the decimal precision shown in the image above, Plan writes back values (in this example, to Snowflake) rounded off to 5 decimal places.

Writeback percentage values

• Text length

When you add destinations, you can restrict text fields to 512 characters or allow writeback up to the maximum limit supported by the backend.

Setting the text length

3. Batch writeback

When you configure individual writeback destinations, you'll notice an option for batched writeback wherever applicable (batched writeback is not possible for destinations like Sharepoint, Rest API, OneDrive, etc). If your writeback payload exceeds 50k records, Plan can split the payload into multiple chunks and write them back batch-by-batch.

You can specify whether you will use a temporary table to hold the batched data.

Temporary staging table configuration

• To use this feature, enable the checkbox as shown in the image above.

• You can specify a custom table name or use the default table created by Plan to store batched data.

You can analyze the writeback log, which will capture how the payload has been split into multiple chunks and processed in parallel for a performance boost.

Writeback logs for batched data