Automate TaxJar Data Replication to Azure Data Lake

Always-on applications rely on automatic failover capabilities and real-time data access. CData Sync integrates live TaxJar data into your Azure Data Lake instance, allowing you to consolidate all of your data into a single location for archiving, reporting, analytics, machine learning, artificial intelligence and more.

Configure Azure Data Lake as a Replication Destination

Using CData Sync, you can replicate TaxJar data to Azure Data Lake. To add a replication destination, navigate to the Connections tab.

1. Click Add Connection.
2. Select Azure Data Lake as a destination.

3. Enter the necessary connection properties. To connect to Azure Data Lake, set the following properties, depending on your version of Azure Data Lake Storage:

   Azure Data Lake Storage Gen1

   • Generation: Must be set to 1.
   • Account: The name of the Azure Data Lake Store account.
   • Path: The path to store the replicated file (the root directory by default).
   • TenantId: The tenant ID.
   • OAuthClientId: The application ID for the Azure Directory web application (see the CData Sync Help for more information).
   • OAuthClientSecret: The key generated for the Azure Directory web application (see the CData Sync Help for more information).

   Azure Data Lake Storage Gen2

   • Generation: Must be set to 2.
   • Access Key: The access key used to authenticate (see the CData Sync Help for more information).
   • Account: The name of the Azure Data Lake Store account.
   • FileSystem: The file systems used for this account.
   • Path: The path to store the replicated file (the root directory by default).
4. Click Test Connection to ensure that the connection is configured properly.
5. Click Save Changes.

Configure the TaxJar Connection

You can configure a connection to TaxJar from the Connections tab. To add a connection to your TaxJar account, navigate to the Connections tab.

1. Click Add Connection.
2. Select a source (TaxJar).
3. Configure the connection properties.
   
   

   To authenticate to the TaxJar API, you will need to first obtain the API Key from the TaxJar UI.

   NOTE: the API is available only for Professional and Premium TaxJar plans.

   If you already have a Professional or Premium plan you can find the API Key by logging in the TaxJar UI and navigating to Account -> TaxJar API. After obtaining the API Key, you can set it in the APIKey connection property.

   Additional Notes

   • By default, the CData connector will retrieve data of the last 3 months in cases where the entity support date range filtering. You can set StartDate to specify the minimum creation date of the data retrieved.
   • If the API Key has been created for a sandbox API account please set UseSandbox to true, but not all endpoints will work as expected. For more information, refer to the TaxJar developer documentation.
4. Click Connect to ensure that the connection is configured properly.
5. Click Save Changes.

Configure Replication Queries

CData Sync enables you to control replication with a point-and-click interface and with SQL queries. For each replication you wish to configure, navigate to the Jobs tab and click Add Job. Select the Source and Destination for your replication.

Replicate Entire Tables

To replicate an entire table, click Add Tables in the Tables section, choose the table(s) you wish to replicate, and click Add Selected Tables.

Customize Your Replication

You can use the Columns and Query tabs of a task to customize your replication. The Columns tab allows you to specify which columns to replicate, rename the columns at the destination, and even perform operations on the source data before replicating. The Query tab allows you to add filters, grouping, and sorting to the replication.

Schedule Your Replication

In the Schedule section, you can schedule a job to run automatically, configuring the job to run after specified intervals ranging from once every 10 minutes to once every month.

Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your TaxJar data to PostgreSQL.