You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+19Lines changed: 19 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,22 @@
1
+
# dbt_sage_intacct_source v0.4.0
2
+
[PR #20](https://github.com/fivetran/dbt_sage_intacct_source/pull/20) includes the following updates:
3
+
4
+
## Breaking Changes
5
+
- Reintroduced `_fivetran_deleted` from the `gl_detail` source table, as the field was not fully deprecated within in the connector.
6
+
**It is null in normal incremental syncs, but can populate true (or false) in historical resyncs.**
7
+
- This ensures the general ledger models in the downstream `dbt_sage_intacct` transform package exclude deleted records from `stg_sage_intacct__gl_detail`.
8
+
- Renamed `_fivetran_deleted` to:
9
+
-`is_batch_deleted` in `stg_sage_intacct__gl_batch`
10
+
-`is_detail_deleted` in `stg_sage_intacct__gl_detail`
11
+
- This ensures column name uniqueness when they are joined into `int_sage_intacct__active_gl_detail` in the `dbt_sage_intacct` package.
12
+
13
+
## Documentation
14
+
- Corrected references to connectors and connections in the README. ([#19](https://github.com/fivetran/dbt_sage_intacct_source/pull/19))
15
+
- Corrected the `_fivetran_deleted` descriptions in the `src_sage_intacct.yml` and `stg_sage_intacct.yml` documentation.
16
+
17
+
## Under the Hood
18
+
- Updated `gl_detail` yml and seed files with `_fivetran_deleted` documentation and records for testing.
19
+
1
20
# dbt_sage_intacct_source v0.3.1
2
21
[PR #16](https://github.com/fivetran/dbt_sage_intacct_source/pull/16) includes the following updates:
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@
22
22
## How do I use the dbt package?
23
23
### Step 1: Prerequisites
24
24
To use this dbt package, you must have the following:
25
-
- At least one Fivetran Sage Intacct connector syncing data into your destination.
25
+
- At least one Fivetran Sage Intacct connection syncing data into your destination.
26
26
- A **BigQuery**, **Snowflake**, **Redshift**, **PostgreSQL**, or **Databricks** destination.
27
27
28
28
#### Databricks Dispatch Configuration
@@ -39,7 +39,7 @@ If you are **not** using the [Sage Intacct transformation package](https://githu
39
39
```yaml
40
40
packages:
41
41
- package: fivetran/sage_intacct_source
42
-
version: [">=0.3.0", "<0.4.0"] # we recommend using ranges to capture non-breaking changes automatically
42
+
version: [">=0.4.0", "<0.5.0"] # we recommend using ranges to capture non-breaking changes automatically
43
43
```
44
44
### Step 3: Define database and schema variables
45
45
By default, this package runs using your destination and the `sage_intacct` schema. If this is not where your Sage Intacct data is (for example, if your Sage Intacct schema is named `sage_intacct_fivetran`), add the following configuration to your root `dbt_project.yml` file:
Copy file name to clipboardExpand all lines: models/src_sage_intacct.yml
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ sources:
19
19
- name: recordno
20
20
description: Unique identity of the entry
21
21
- name: _fivetran_deleted
22
-
description: The timestamp of when the data was deleted by Fivetran
22
+
description: Boolean field indicating whether the record was deleted. Due to source limitations, this field is currently populated with `nulls` in incremental syncs in Fivetran. In historical resyncs, it may be populated with `true` or `false`.
23
23
- name: _fivetran_synced
24
24
description: The timestamp of when the data was last synced by Fivetran
25
25
- name: accountno
@@ -101,7 +101,7 @@ sources:
101
101
- name: recordno
102
102
description: Unique identity of the entry
103
103
- name: _fivetran_deleted
104
-
description: The timestamp of when the data was deleted by Fivetran
104
+
description: Boolean field indicating whether the record was deleted.
105
105
- name: _fivetran_synced
106
106
description: The timestamp of when the data was last synced by Fivetran
107
107
- name: accountno
@@ -165,7 +165,7 @@ sources:
165
165
- name: recordno
166
166
description: Unique identity of the entry
167
167
- name: _fivetran_deleted
168
-
description: The timestamp of when the data was deleted by Fivetran
168
+
description: Boolean field indicating whether the record was deleted.
169
169
- name: _fivetran_synced
170
170
description: The timestamp of when the data was last synced by Fivetran
171
171
- name: auwhencreated
@@ -307,7 +307,7 @@ sources:
307
307
- name: recordno
308
308
description: Unique identity of the entry
309
309
- name: _fivetran_deleted
310
-
description: The timestamp of when the data was deleted by Fivetran
310
+
description: Boolean field indicating whether the record was deleted.
311
311
- name: _fivetran_synced
312
312
description: The timestamp of when the data was last synced by Fivetran
313
313
- name: auwhencreated
@@ -449,7 +449,7 @@ sources:
449
449
description: Records batch updates of records originating from the gl_detail table
450
450
columns:
451
451
- name: _fivetran_deleted
452
-
description: The timestamp of when the data was deleted by Fivetran
452
+
description: Boolean field indicating whether the record was deleted.
453
453
- name: _fivetran_synced
454
454
description: The timestamp of when the data was last synced by Fivetran
0 commit comments