dbt_salesforce

KO | EN

gitlite — search

#python #java #javascript #android #php #elixir #hacktoberfest #opengl #fun #kotlin #generator #eslint

★ 53 Open GitHub ↗

Fivetran's Salesforce dbt package

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Salesforce dbt Package

This dbt package transforms data from Fivetran's Salesforce connector into analytics-ready tables.

## Resources

- Number of materialized models¹: 27
- Connector documentation
 - [Salesforce connector documentation](https://fivetran.com/docs/connectors/applications/salesforce)
 - [Salesforce ERD](https://fivetran.com/docs/connectors/applications/salesforce#schemainformation)
- dbt package documentation
 - [GitHub repository](https://github.com/fivetran/dbt_salesforce)
 - [dbt Docs](https://fivetran.github.io/dbt_salesforce/#!/overview)
 - [DAG](https://fivetran.github.io/dbt_salesforce/#!/overview?g_v=1)
 - [Changelog](https://github.com/fivetran/dbt_salesforce/blob/main/CHANGELOG.md)
- dbt Core™ supported versions
 - `>=1.3.0, <3.0.0`

## What does this dbt package do?
This package enables you to understand opportunity performance, analyze sales team performance, and track daily sales activities. It creates enriched models with metrics focused on pipeline management, bookings analysis, and historical tracking.

**Note**: This package also provides you with the option to leverage the history mode to gather historical records of your essential tables.

### Output schema
Final output tables are generated in the following target schema:

```
<your_database>.<connector/schema_name>_salesforce
```

### Final output tables

By default, this package materializes the following final tables:

| Table | Description |
| :---- | :---- |
| [salesforce__manager_performance](https://fivetran.github.io/dbt_salesforce/#!/model/model.salesforce.salesforce__manager_performance) | This table provides performance metrics by manager, showing team level pipeline, bookings, losses, and win rates. **Example Analytics Questions:** <ul><li>How do team size and composition relate to overall bookings and pipeline coverage by manager?</li><li>Which managers demonstrate consistently strong conversion rates, and what common practices can be scaled across teams?</li></ul> |
| [salesforce__owner_performance](https://fivetran.github.io/dbt_salesforce/#!/model/model.salesforce.salesforce__owner_performance) | This table provides an enhanced view of individual sales team members, including metrics around bookings, pipeline, losses, and win percentage. **Example Analytics Questions:** <ul><li>How does quota attainment vary by tenure, role, or territory?</li><li>What activity and pipeline patterns are most strongly associated with high win rates?</li></ul> |
| [salesforce__sales_snapshot](https://fivetran.github.io/dbt_salesforce/#!/model/model.salesforce.salesforce__sales_snapshot) | This table provides a single-row snapshot of current and all-time sales funnel metrics. **Example Analytics Questions:** <ul><li>What long-term changes are visible in win rates, deal size, or funnel velocity?</li><li>How does our current pipeline coverage compare to historical benchmarks for achieving quarterly targets?</li></ul> |
| [salesforce__opportunity_enhanced](https://fivetran.github.io/dbt_salesforce/#!/model/model.salesforce.salesforce__opportunity_enhanced) | This table enriches opportunities with data about the associated account, opportunity owner, and record type. **Example Analytics Questions:** <ul><li>Which industries or account types generate the highest-value opportunities and shortest sales cycles?</li><li>Which opportunities have been open the longest and what intervention strategies could help close them?</li></ul> |
| [salesforce__contact_enhanced](https://fivetran.github.io/dbt_salesforce/#!/model/model.salesforce.salesforce__contact_enhanced) | This table enriches contacts with information about the associated account and contact owner. **Example Analytics Questions:** <ul><li>Do opportunities with multiple engaged contacts close faster or larger?</li><li>Which contact attributes are most commonly present in successfully closed opportunities?</li></ul> |
| [salesforce__daily_activity](https://fivetran.github.io/dbt_salesforce/#!/model/model.salesforce.salesforce__daily_activity) | This table provides a daily summary of sales activities related to the creation and conversion of leads, tasks, and opportunities. **Example Analytics Questions:** <ul><li>How does the mix of tasks versus events impact overall sales productivity and outcomes?</li><li>Which days of the week or times of year show the highest conversion rates from activities to opportunities?</li></ul> |
| [salesforce__opportunity_line_item_enhanced](https://fivetran.github.io/dbt_salesforce/#!/model/model.salesforce.salesforce__opportunity_line_item_enhanced) | This table showcases individual line items belonging to opportunities and adds associated product details. **Example Analytics Questions:** <ul><li>What were the most popularly bundled products last quarter across different customer segments?</li><li>Which accounts show early warning signs of churn based on historical patterns?</li></ul> |
| [salesforce__campaign_performance](https://fivetran.github.io/dbt_salesforce/#!/model/model.salesforce.salesforce__campaign_performance) | This table provides campaign attribution metrics connecting campaign data to pipeline, revenue, and member engagement outcomes. Metrics include won revenue, member counts, response rates, and ROI. **Example Analytics Questions:** <ul><li>Which campaigns drove the most won revenue and pipeline?</li><li>What is the cost per won opportunity and ROI for each campaign type?</li></ul> |
| [salesforce__account_daily_history](https://fivetran.github.io/dbt_salesforce/#!/model/model.salesforce.salesforce__account_daily_history) | **Not currently available in Quickstart:** This table provides a daily record of each account, starting with its first active date and extending to its last active date, or the current date if the account is still active. **Example Analytics Questions:** <ul><li>How do account engagement levels fluctuate around contract renewal periods?</li><li>What account changes most commonly precede upsell or cross-sell opportunities?</li></ul> |
| [salesforce__contact_daily_history](https://fivetran.github.io/dbt_salesforce/#!/model/model.salesforce.salesforce__contact_daily_history) | **Not currently available in Quickstart:** This table provides a daily record of each contact, starting with its first active date and extending to its last active date, or the current date if the contact is still active. **Example Analytics Questions:** <ul><li>How do contact engagement patterns change throughout the sales cycle?</li><li>How do contact role changes within accounts impact ongoing sales opportunities?</li></ul> |
| [salesforce__opportunity_daily_history](https://fivetran.github.io/dbt_salesforce/#!/model/model.salesforce.salesforce__opportunity_daily_history) | **Not currently available in Quickstart:** This table provides a daily record of each opportunity, starting with its first active date and extending to its last active date, or the current date if the opportunity is still active. **Example Analytics Questions:** <ul><li>What are the typical progression patterns for opportunities that ultimately close-won versus close-lost?</li><li>Which stage transitions take the longest and represent the biggest bottlenecks in our sales process?</li></ul> |
| [salesforce__campaign_daily_history](https://fivetran.github.io/dbt_salesforce/#!/model/model.salesforce.salesforce__campaign_daily_history) | **Not currently available in Quickstart:** This table provides a daily record of each campaign, starting with its first active date and extending to its last active date, or the current date if the campaign is still active. **Example Analytics Questions:** <ul><li>How have campaign budgets and actual costs changed over the course of a campaign?</li><li>How did campaign status and member counts evolve throughout the campaign lifecycle?</li></ul> |

**Note**: For Quickstart Data Model users only, in addition to the above output models that are Quickstart compatible, you will also receive models in your transformation list which replicate **all** of your Salesforce objects with the inclusion of the relevant formula fields in the generated output models.

¹ Each Quickstart transformation job run materializes these models if all components of this data model are enabled. This count includes all staging, intermediate, and final models materialized as `view`, `table`, or `incremental`.

---

## Prerequisites
To use this dbt package, you must have the following:

- At least one Fivetran Salesforce connection syncing data into your destination.
- A BigQuery, Snowflake, Redshift, PostgreSQL, or Databricks destination.

## How do I use the dbt package?
You can either add this dbt package in the Fivetran dashboard or import it into your dbt project:

- To add the package in the Fivetran dashboard, follow our [Quickstart guide](https://fivetran.com/docs/transformations/data-models/quickstart-management).
- To add the package to your dbt project, follow the setup instructions in the dbt package's [README file](https://github.com/fivetran/dbt_salesforce/blob/main/README.md#how-do-i-use-the-dbt-package) to use this package.

### Installing the Package
Include the following salesforce package version in your `packages.yml`
> Check [dbt Hub](https://hub.getdbt.com/) for the latest installation instructions, or [read the dbt docs](https://docs.getdbt.com/docs/package-management) for more information on installing packages.
```yaml
packages:
 - package: fivetran/salesforce
 version: [">=2.4.0", "<2.5.0"] # we recommend using ranges to capture non-breaking changes automatically
```

> All required sources and staging models are now bundled into this transformation package. Do not include `fivetran/salesforce_source` in your `packages.yml` since this package has been deprecated.

#### Databricks Dispatch Configuration
If you are using a Databricks destination with this package you will need to add the below (or a variation of the below) dispatch configuration within your `dbt_project.yml`. This is required in order for the package to accurately search for macros within the `dbt-labs/spark_utils` then the `dbt-labs/dbt_utils` packages respectively.
```yml
dispatch:
  - macro_namespace: dbt_utils
    search_order: ['spark_utils', 'dbt_utils']
```
#### Database Incremental Strategies
The history end models in this package are materialized incrementally. We have chosen `insert_overwrite` as the default strategy for **BigQuery** and **Databricks** databases, as it is only available for these dbt adapters. For **Snowflake**, **Redshift**, and **Postgres** databases, we have chosen `delete+insert` as the default strategy.

`insert_overwrite` is our preferred incremental strategy because it will be able to properly handle updates to records that exist outside the immediate incremental window. That is, because it leverages partitions, `insert_overwrite` will appropriately update existing rows that have been changed upstream instead of inserting duplicates of them--all without requiring a full table scan.

`delete+insert` is our second-choice as it resembles `insert_overwrite` but lacks partitions. This strategy works most of the time and appropriately handles incremental loads that do not contain changes to past records. However, if a past record has been updated and is outside of the incremental window, `delete+insert` will insert a duplicate record.
> Because of this, we highly recommend that **Snowflake**, **Redshift**, and **Postgres** users periodically run a `--full-refresh` to ensure a high level of data quality and remove any possible duplicates.

### Configure Your Variables
#### Database and Schema Variables
By default, this package will run using your target database and the `salesforce` schema. If this is not where your Salesforce data is, add the following configuration to your root `dbt_project.yml` file:

```yml
vars:
    salesforce_database: your_database_name    
    salesforce_schema: your_schema_name
```

#### Disabling Models
Your Salesforce connection may not sync every table that this package expects. If your syncs exclude certain tables, it is because you either don't use that functionality in Salesforce or actively excluded some tables from your syncs.

To disable the corresponding functionality in this package, you must add the corresponding variable(s) to your `dbt_project.yml`, which are listed below. By default, that is if none of these variables are added, all variables are assumed to be true. Add variables only for the tables you would like to disable:

```yml
vars:
  salesforce__user_role_enabled: false # Disable if you do not have the user_role table
  salesforce__lead_enabled: false # Disable if you do not have the lead table
  salesforce__event_enabled: false # Disable if you do not have the event table
  salesforce__task_enabled: false # Disable if you do not have the task table
  salesforce__opportunity_line_item_enabled: false # Disable if you do not have the opportunity_line_item table
  salesforce__order_enabled: false # Disable if you do not have the order table
  salesforce__product_2_enabled: false # Disable if you do not have the product_2 table
```
The corresponding metrics from the disabled tables will not populate in the downstream models.

#### Working without an `OPPORTUNITY` Table
If you do not have the `OPPORTUNITY` table, there is no variable to turn off opportunity-related transformations, as this table is largely the backbone of the Salesforce package.

However, you may still find value in this package without opportunity data, specifically in the `salesforce__contact_enhanced`, `salesforce__daily_activity`, `salesforce__account_daily_history` and `salesforce__contact_daily_history` (if using History Mode) end models.

For this use case, to ensure the package runs successfully, we recommend leveraging this [Fivetran Feature](https://fivetran.com/docs/using-fivetran/features#syncingemptytablesandcolumns) to create an empty `opportunity` table. To do so, follow these steps:
1. Navigate to your Salesforce connection in the "Connectors" tab within the Fivetran UI.
2. Click on the "Schema" tab.
3. Scroll down to `Opportunity` and click on its checkbox to add it into your schema.
4. Click "Save Changes" in the upper righthand corner of the screen.
5. Either click "Resync" for the `Opportunity` table specifically or wait for your next connection-level sync.

> Note that all other end models (`salesforce__opportunity_enhanced`, `salesforce__opportunity_line_item_enhanced`, `salesforce__manager_performance`, `salesforce__owner_performance`, `salesforce__sales_snapshot`, and `salesforce__opportunity_daily_history`) will still materialize after a blanket `dbt run` but will be largely empty/null.

### (Optional) Utilizing Salesforce History Mode records
If you have Salesforce [History Mode](https://fivetran.com/docs/using-fivetran/features#historymode) enabled for your connection, we now include support for the `account`, `campaign`, `contact`, and `opportunity` tables directly in our daily history models. This will allow you access to your historical data for these tables while taking advantage of incremental loads to help with compute.

#### IMPORTANT: How To Update Your History Models
To ensure maximum value for these history mode models and avoid messy historical data that could come with picking and choosing which fields you bring in, **all fields in your Salesforce history mode connection are being synced into your end daily history models**. That means all custom fields you picked to sync are being brought in to the final models. [See our DECISIONLOG for more details on why we are bringing in all fields](https://github.com/fivetran/dbt_salesforce/blob/main/DECISIONLOG.md).

To update the history mode models, you must follow these steps:
1) Go to your Fivetran Salesforce History Mode connection page.
2) Update the fields that you are bringing into the model.
3) Run a `dbt run --full-refresh` on the specific daily history models you've updated to bring in these fields and all the historical data available with these fields.

We are aware that bringing in additional fields will be very process-heavy, so we do emphasize caution in making changes to your history mode connection. It would be best to batch as many field changes as possible before executing a `--full-refresh` to save on processing.

#### Configuring Your Salesforce History Mode Database and Schema Variables
Customers with a Salesforce connection generally fall into one of two categories when taking advantage of History mode. They either have one connection that is syncing non-historical records and a separate connection that syncs historical records, **or** they have one connection that is syncing historical records. We have designed this feature to support both scenarios.

##### Option 1: Two connections, one with non-historical data and another with historical data
If you are gathering data from both standard Salesforce as well as Salesforce History Mode, and your target database and schema differ as well, you will need to add an additional configuration for the history schema and database to your `dbt_project.yml`.

```yml
vars:
    salesforce_database: your_database_name # salesforce by default
    salesforce_schema: your_schema_name

salesforce_history_database: your_history_database_name # salesforce_history by default
    salesforce_history_schema: your_history_schema_name
```

##### Option 2: One connection being used to sync historical data
Perhaps you may only want to use the Salesforce History Mode to bring in your data. Because the Salesforce schema is pointing to the default `salesforce` schema and database, you will want to add the following variable into your `dbt_project.yml` to point it to the `salesforce_history` equivalents.

```yml
vars:
    salesforce_database: your_history_database_name # salesforce by default
    salesforce_schema: your_history_schema_name

salesforce_history_database: your_history_database_name # salesforce_history by default
    salesforce_history_schema: your_history_schema_name
```

**IMPORTANT**: If you utilize Option 2, you must sync the equivalent enabled tables and fields in your history mode connection that are being brought into your end reports. Examine your data lineage and the model fields within the `salesforce` folder to see which tables and fields you are using and need to bring in and sync in the history mode connection.

#### Enabling Salesforce History Mode Models
The History Mode models can get quite expansive since it will take in **ALL** historical records, so we've disabled them by default. You can enable the history models you'd like to utilize by adding the below variable configurations within your `dbt_project.yml` file for the equivalent models.

```yml
# dbt_project.yml

vars:
  salesforce__account_history_enabled: true  # False by default. Only use if you have history mode enabled and wish to view the full historical record of all your synced account fields, particularly in the daily account history model.
  salesforce__campaign_history_enabled: true  # False by default. Only use if you have history mode enabled and wish to view the full historical record of all your synced campaign fields, particularly in the daily campaign history model.
  salesforce__contact_history_enabled: true  # False by default. Only use if you have history mode enabled and wish to view the full historical record of all your synced contact fields, particularly in the daily contact history model.
  salesforce__opportunity_history_enabled: true  # False by default. Only use if you have history mode enabled and wish to view the full historical record of all your synced opportunity fields, particularly in the daily opportunity history model.
```

#### Filter your Salesforce History Mode models with field variable conditionals
By default, these models are set to bring in all your data from Salesforce History, but you may be interested in bringing in only a smaller sample of historical records, given the relative size of the Salesforce History source tables. By default, the package will use `2020-01-01` as the minimum date for the historical end models. This date was chosen to ensure there was a limit to the amount of historical data processed on first run. This default may be overwritten to your liking by leveraging the below variables.

We have set up where conditions in our staging models to allow you to bring in only the data you need to run in. You can set a global history filter that would apply to all of our staging history models in your `dbt_project.yml`:

```yml 
vars:
    global_history_start_date: 'YYYY-MM-DD' # The first `_fivetran_start` date you'd like to filter data on in all your history models.
```

If you'd like to apply model-specific conditionals, configure the below variables in your `dbt_project.yml`:

```yml 
vars:
    account_history_start_date: 'YYYY-MM-DD' # The first date in account history you wish to pull records from, filtering on `_fivetran_start`.
    campaign_history_start_date: 'YYYY-MM-DD' # The first date in campaign history you wish to pull records from, filtering on `_fivetran_start`.
    contact_history_start_date: 'YYYY-MM-DD' # The first date in contact history you wish to pull records from, filtering on `_fivetran_start`.
    opportunity_history_start_date: 'YYYY-MM-DD' # The first date in opportunity history you wish to pull records from, filtering on `_fivetran_start`.
```

#### Adjusting the Incremental Lookback Window
Corrected or backfilled history records may occasionally arrive after the date they apply to has already been materialized. To pick these up without requiring a full refresh, the `salesforce__account_daily_history`, `salesforce__campaign_daily_history`, `salesforce__contact_daily_history`, and `salesforce__opportunity_daily_history` models reprocess a small window of already-materialized dates on every incremental run, in addition to any new dates.

To change the default lookback window, add the following variable to your `dbt_project.yml` file:

```yml
vars:
    lookback_window: number_of_days # default is 1
```

> Corrections landing further back than the configured lookback window will still require a `--full-refresh` on the affected model(s) to be picked up.

### (Optional) Additional Configurations
#### Change the Source Table References
Source tables are referenced using default names. If an individual source table has a different name than expected, provide the name of the table as it appears in your warehouse to the respective variable:
> IMPORTANT: See the package's source [`dbt_project.yml`](https://github.com/fivetran/dbt_salesforce/blob/main/dbt_project.yml) variable declarations to see the expected names.

```yml
vars:
 <package_name>_<default_source_table_name>_identifier: your_table_name
```

#### Change the Build Schema
By default, this package builds all of the Salesforce models within your `target.schema` in your target database. If this is not where you would like your Salesforce data to be written to, add the following configuration to your root `dbt_project.yml` file:

```yml
models:
 salesforce: # If you want everything written to one schema, you can scope the +schema config to the package level
 salesforce:
 +schema: my_new_schema_name # Will write Salesforce end models to <target_schema> + _my_new_schema_name
 staging:
 +schema: my_new_schema_name # Will write Salesforce staging models to <target_schema> + _my_new_schema_name
 salesforce_history:
 +schema: my_new_schema_name # Will write Salesforce History models to <target_schema> + _my_new_schema_name
```

#### Adding Passthrough Columns
This package allows users to add additional columns to the `salesforce__opportunity_enhanced`, `salesforce__opportunity_line_item_enhanced`, `salesforce__contact_enhanced`, `salesforce__campaign_performance`, and any of the `daily_history` models if you have Salesforce history mode enabled. You can do this by using the below variables in your `dbt_project.yml` file. These variables allow these additional columns to be aliased (`alias`) and casted (`transform_sql`) if desired, but not required. Datatype casting is configured via a sql snippet within the `transform_sql` key. You may add the desired sql while omitting the `as field_name` at the end and your custom pass-though fields will be casted accordingly. Use the below format for declaring the respective pass-through variables.

For the `salesforce__opportunity_enhanced` model, it joins in the `user` model two times, since an opportunity has both an owner and manager. The first time the `user` model is joined is to add information about an opportunity owner. The second time is to add information about an opportunity manager. Therefore to avoid ambiguous columns from joining in the same model twice, custom fields passed through from the user table will be suffixed based on whether it belongs to a user who is an `_owner` or a `_manager`.

Additionally, you may add additional columns to the staging models. For example, for passing columns to `stg_salesforce__product_2` you would need to configure `salesforce__product_2_pass_through_columns`.

```yml
# dbt_project.yml

vars:
  salesforce__account_pass_through_columns: 
    - name: "salesforce__account_field"
      alias: "renamed_field"
      transform_sql: "cast(renamed_field as string)"
  salesforce__contact_pass_through_columns: 
    - name: "salesforce__contact_field"
      alias: "contact_field_x"
  salesforce__event_pass_through_columns: 
    - name: "salesforce__event_field"
      transform_sql: "cast(salesforce__event_field as int64)"
  salesforce__lead_pass_through_columns: 
    - name: "salesforce__lead_field"
  salesforce__opportunity_pass_through_columns: 
    - name: "salesforce__opportunity_field"
      alias: "opportunity_field_x"
  salesforce__opportunity_line_item_pass_through_columns: 
    - name: "salesforce__opportunity_line_item_field"
      alias: "opportunity_line_item_field_x"
    - name: "field_name_2"
  salesforce__order_pass_through_columns: 
    - name: "salesforce__order_field"
      alias: "order_field_x"
    - name: "another_field"
      alias: "field_abc"
  salesforce__product_2_pass_through_columns: 
    - name: "salesforce__product_2_field"
      alias: "product_2_field_x"
  salesforce__task_pass_through_columns: 
    - name: "salesforce__task_field"
      alias: "task_field_x"
  salesforce__user_role_pass_through_columns: 
    - name: "salesforce__user_role_field"
      alias: "user_role_field_x"
  salesforce__user_pass_through_columns: 
    - name: "salesforce__user_field"
  salesforce__campaign_pass_through_columns: 
    - name: "salesforce__campaign_field"
      alias: "campaign_field_x"
```

> **NOTE:** If you are creating a passthrough column that applies `transform_sql` to a field already included by default, you must capitalize the `name` value like such:
> 
```yml
  salesforce__lead_pass_through_columns:
    - name: "Email" # instead of email
      alias: "email_domain"
      transform_sql: "split(email_domain, '@')[0]"
```

### (Optional) Adding Formula Fields as Pass Through Columns
#### Adding Formula Fields as Pass Through Columns
The source tables Fivetran syncs do not include formula fields. If your company uses them, you can generate them by referring to the [Salesforce Formula Utils](https://github.com/fivetran/dbt_salesforce_formula_utils) package. To pass through the fields, add the [latest version of the package](https://github.com/fivetran/dbt_salesforce_formula_utils#installing-the-macro-package). We recommend confirming your formula field models successfully populate before integrating with the Salesforce package.

Include the following within your `dbt_project.yml` file:
```yml
# Using the opportunity source table as example, update the opportunity variable to reference your newly created model that contains the formula fields:
  salesforce_opportunity_identifier: "'my_new_opportunity_formula_table'"

# In addition, add the desired field names as pass through columns
  salesforce__opportunity_pass_through_columns:
    - name: "salesforce__opportunity_field"
      alias: "opportunity_field_x"
```

### (Optional) Orchestrate your models with Fivetran Transformations for dbt Core™
Fivetran offers the ability for you to orchestrate your dbt project through the [Fivetran Transformations for dbt Core™](https://fivetran.com/docs/transformations/dbt#transformationsfordbtcore) product. Refer to the linked docs for more information on how to setup your project for orchestration through Fivetran.

## Does this package have dependencies?
This dbt package is dependent on the following dbt packages. For more information on the below packages, refer to the [dbt hub](https://hub.getdbt.com/) site.
> **If you have any of these dependent packages in your own `packages.yml` I highly recommend you remove them to ensure there are no package version conflicts.**
```yml
packages:
 - package: fivetran/fivetran_utils
 version: [">=0.4.0", "<0.5.0"]
 - package: dbt-labs/dbt_utils
 version: [">=1.0.0", "<2.0.0"]
 - package: dbt-labs/spark_utils
 version: [">=0.3.0", "<0.4.0"]
```

## How is this package maintained and can I contribute?

### Package Maintenance
The Fivetran team maintaining this package only maintains the [latest version](https://hub.getdbt.com/fivetran/salesforce/latest/) of the package. We highly recommend you stay consistent with the latest version of the package and refer to the [CHANGELOG](https://github.com/fivetran/dbt_salesforce/blob/main/CHANGELOG.md) and release notes for more information on changes across versions.

### Contributions
A small team of analytics engineers at Fivetran develops these dbt packages. However, the packages are made better by community contributions.

We highly encourage and welcome contributions to this package. Learn how to contribute to a package in dbt's [Contributing to an external dbt package article](https://discourse.getdbt.com/t/contributing-to-a-dbt-package/657).

## Are there any resources available?
- If you encounter any questions or want to reach out for help, see the [GitHub Issue](https://github.com/fivetran/dbt_salesforce/issues/new/choose) section to find the right avenue of support for you.
- If you would like to provide feedback to the dbt package team at Fivetran, or would like to request a future dbt package to be developed, then feel free to fill out our [Feedback Form](https://www.surveymonkey.com/r/DQ7K7WW).

dbt_salesforce

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README