Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Add Quickstart Model Counts to README #54

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Feature: Add Quickstart Model Counts to README #54

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,10 @@
# dbt_salesforce_source version.version

## Documentation
- Corrected references to connectors and connections in the README. ([#54](https://github.com/fivetran/dbt_salesforce_source/pull/54))

# dbt_salesforce_source version.version

## Documentation
- Minor README updates
- Updated macro comments to provide clearer and more detailed explanations of the workflow.
Expand Down
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@

## How do I use the dbt package?
### Step 1: Pre-Requisites
- **Connector**: Have the Fivetran Salesforce connector syncing data into your warehouse.
- At least one Fivetran Salesforce connection syncing data into your destination.
- **Database support**: This package has been tested on **Postgres**, **Databricks**, **Redshift**, **Snowflake**, and **BigQuery**.

#### Databricks Dispatch Configuration
Expand Down Expand Up @@ -87,7 +87,7 @@ If you have Salesforce [History Mode](https://fivetran.com/docs/using-fivetran/f
#### Configuring Your Salesforce History Mode Database and Schema Variables
Customers leveraging the Salesforce connector generally fall into one of two categories when taking advantage of History mode. They either have one connector that is syncing non-historical records and a separate connector that syncs historical records, **or** they have one connector that is syncing historical records. We have designed this feature to support both scenarios.

##### Option 1: Two connectors, one with non-historical data and another with historical data
##### 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
Expand Down