BigCommerce Advanced Settings

For users who have some experience working with their data in Panoply, there are a number of items that can be customized for this data source.

1. Destination Schema: This is the name of the target schema to save the data. For warehouses built on Amazon Redshift, the default schema is Public. For warehouses built on Google BigQuery, the default schema is Panoply This cannot be changed once a source had been collected.
2. Destination Prefix: This is the prefix that Panoply will use in the name of the tables included in the collection.
   • The default prefix for BigCommerce is bigcommerce. To change this, entire your desired prefix.
   • The naming convention is bigcommerce_<__store>_<__resource>, where both __resource is a dynamic field based on the selected end point and __store is the connected store. For example, for the resource named coupons, and the business name is my_store, the default destination table will be bigcommerce_my_store_coupons.
3. Incremental Load: By default, Panoply collects all of your data from BigCommerce on your first collect. After that, Panoply collects from the date of the last successful collection where possible.
4. Exclude: The Exclude option allows you to exclude certain data, such as names, addresses, or other personally identifiable information. Enter the column names of the data to exclude.
5. Truncate: Truncate deletes all the current data stored in the destination tables, but not the tables themselves. Afterwards Panoply will recollect all the available data for this data source.
6. Click Save Changes then click Collect.
   • The data source appears grayed out while the collection runs.
   • You may add additional data sources while this collection runs.
   • You can monitor this collection from the Jobs page or the Data Sources page.
   • After a successful collection, navigate to the Tables page to review the data results.