Skip to content

Commit

Permalink
Merge pull request #2 from jlmendgom5TRAN/patch-1
Browse files Browse the repository at this point in the history
doc(dbt): dbt sage intacct source edited for Fivetran style
  • Loading branch information
fivetran-reneeli authored Mar 18, 2022
2 parents 922139d + 5d6603c commit 873cbbb
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,11 +9,11 @@ This package enriches your Fivetran data by doing the following:
- Models staging tables, which will be used in our transform package

## Models
This package contains staging models, designed to work simultaneously with our [Sage Intacct transform package](https://github.com/fivetran/dbt_sage_intacct). The staging models are designed to:
This package contains staging models, designed to work simultaneously with our [Sage Intacct transform package](https://github.com/fivetran/dbt_sage_intacct). The staging models are designed to:
- Remove any rows that are soft-deleted
- Name columns consistently across all packages:
- Boolean fields are prefixed with `is_` or `has_`
- Timestamps are appended with `_at`
- Boolean fields are prefixed with `is_` or `has_`.
- Timestamps are appended with `_at`.
- ID primary keys are prefixed with the name of the table. For example, the `gl_detail` table's recordno column is renamed `gl_detail_id`.
- Foreign keys include the table that they refer to. For example, ap_bill_item's `recordkey` is named `bill_id`.

Expand Down Expand Up @@ -99,4 +99,4 @@ dispatch:
- Check out [Discourse](https://discourse.getdbt.com/) for commonly asked questions and answers
- Join the [chat](http://slack.getdbt.com/) on Slack for live discussions and support
- Find [dbt events](https://events.getdbt.com) near you
- Check out [the dbt blog](https://blog.getdbt.com/) for the latest news on dbt's development and best practices
- Check out [the dbt blog](https://blog.getdbt.com/) for the latest news on dbt's development and best practices

0 comments on commit 873cbbb

Please sign in to comment.