Xero Advanced Settings
  • 24 May 2023
  • 1 Minute to read
  • Dark
    Light
  • PDF

Xero Advanced Settings

  • Dark
    Light
  • PDF

Article summary

Warning:

We do not recommend changing advanced settings unless you are an experienced Panoply user.

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. Incremental Load:  By default, Panoply collects all of your data from Xero on your first collect. After that, Panoply collects from the date of the last successful collection.
  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 Xero is xero. To change this, enter your desired prefix.
    • The naming convention is xero_<__resource>, where __resource is a dynamic field. For example, for the resource named Accounts, the default destination table will be xero_accounts.
  3. Destination Schema: This is the name of the target schema to save the data. The default schema for data warehouses built on Google BigQuery is panoply. The default schema for data warehouses built on Amazon Redshift is public. This cannot be changed once a source has been collected.
  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. Lock Schema: Lock schema will block any tables' shcema changes like adding new columns, changing of data types or adding new tables.
  7. Load Strategy: Control the ingestion behavior of existing records. You can either set it to Upsert (Update existing and insert new records) or Append (Always insert the records). The default strategy is Upsert.
  8. Nested Data: Control the ingestion behavior of nested objects. You can either set it to create one-to-many tables (default behavior) or flatten the nested data to the parent table
  9. 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.

Was this article helpful?