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: .github/ISSUE_TEMPLATE/bug-report.yml
+21-2Lines changed: 21 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
name: 🐞 Bug
2
2
description: Report a bug or an issue you've found within the dbt package
3
3
title: "[Bug] <title>"
4
-
labels: ["bug", "triage"]
4
+
labels: ["type:bug"]
5
5
body:
6
6
- type: markdown
7
7
attributes:
@@ -35,6 +35,12 @@ body:
35
35
description: A concise description of what you expected to happen.
36
36
validations:
37
37
required: true
38
+
- type: textarea
39
+
attributes:
40
+
label: Possible solution
41
+
description: Were you able to investigate and/or discover a potential fix to this bug in your investigation? If so, it would be much appreciated if you could submit code samples to show us how your fix resolved this issue.
42
+
validations:
43
+
required: false
38
44
- type: textarea
39
45
attributes:
40
46
label: dbt Project configurations
@@ -61,6 +67,19 @@ body:
61
67
- other (mention it in "Additional Context")
62
68
validations:
63
69
required: true
70
+
- type: dropdown
71
+
id: orchestration_type
72
+
attributes:
73
+
label: How are you running this dbt package?
74
+
multiple: true
75
+
options:
76
+
- Fivetran Quickstart Data Model
77
+
- Fivetran Transformations
78
+
- dbt Core™
79
+
- dbt Cloud™
80
+
- other (mention it in "Additional Context")
81
+
validations:
82
+
required: true
64
83
- type: textarea
65
84
attributes:
66
85
label: dbt Version
@@ -83,6 +102,6 @@ body:
83
102
description: Our team will assess this issue and let you know if we will add it to a future sprint. However, if you would like to expedite the solution, we encourage you to contribute to the package via a PR. Our team will then work with you to approve and merge your contributions as soon as possible.
84
103
options:
85
104
- label: Yes.
86
-
- label: Yes, but I will probably need assistance.
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/feature-request.yml
+9-2Lines changed: 9 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
name: 🎉 Feature
2
2
description: Suggest a new feature for the Fivetran dbt package
3
3
title: "[Feature] <title>"
4
-
labels: ["enhancement"]
4
+
labels: ["type:enhancement"]
5
5
body:
6
6
- type: markdown
7
7
attributes:
@@ -20,6 +20,13 @@ body:
20
20
description: A clear and concise description of what you want to happen and why you want the new feature.
21
21
validations:
22
22
required: true
23
+
- type: textarea
24
+
attributes:
25
+
label: How would you implement this feature?
26
+
description: |
27
+
How would you build out this feature with your existing data? Any code examples you can provide to help accelerate development on this issue?
28
+
validations:
29
+
required: true
23
30
- type: textarea
24
31
attributes:
25
32
label: Describe alternatives you've considered
@@ -34,7 +41,7 @@ body:
34
41
description: Our team will assess this feature and let you know if we will add it to a future sprint. However, if you would like to expedite the feature, we encourage you to contribute to the package via a PR. Our team will then work with you to approve and merge your contributions as soon as possible.
35
42
options:
36
43
- label: Yes.
37
-
- label: Yes, but I will probably need assistance.
Copy file name to clipboardExpand all lines: .github/pull_request_template.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,13 @@
19
19
<!--- To select a checkbox you simply need to add an "x" with no spaces between the brackets (eg. [x] Yes). -->
20
20
-[ ] Yes
21
21
22
-
**Provide an emoji that best describes your current mood**
22
+
**Typically there are additional maintenance changes required before this will be ready for an upcoming release. Are you comfortable with the Fivetran team making a few commits directly to your branch?**
23
+
<!--- If you select Yes this will help expedite your PR in case there are small changes required before approval. We encourage you not to use this branch in a production environment as we may make additional updates. -->
24
+
<!--- If you select No, we will not make any changes directly to your branch and will either communicate any planned changes via the PR thread or will merge your PR into a separate branch so we may make changes without modifying your branch.. -->
25
+
-[ ] Yes
26
+
-[ ] No
27
+
28
+
**If you had to summarize this PR in an emoji, which would it be?**
23
29
<!--- For a complete list of markdown compatible emojis check our this git repo (https://gist.github.com/rxaviers/7360908) -->
- Materializes [Netsuite staging tables](https://fivetran.github.io/dbt_netsuite_source/#!/overview/netsuite_source/models/?g_v=1&g_e=seeds) which leverage data in the format described by [this ERD](https://fivetran.com/docs/applications/netsuite#schemainformation). These staging tables clean, test, and prepare your Netsuite data from [Fivetran's connector](https://fivetran.com/docs/applications/netsuite) for analysis by doing the following:
20
20
- Name columns for consistency across all packages and for easier analysis
@@ -24,10 +24,10 @@
24
24
- These tables are designed to work simultaneously with our [Netsuite transformation package](https://github.com/fivetran/dbt_netsuite).
25
25
<!--section-end-->
26
26
27
-
#🎯 How do I use the dbt package?
28
-
## Step 1: Prerequisites
27
+
##How do I use the dbt package?
28
+
###Step 1: Prerequisites
29
29
To use this dbt package, you must have At least either one Fivetran **Netsuite** (netsuite.com) or **Netsuite2** (netsuite2) connector syncing the respective tables to your destination:
30
-
### Netsuite.com
30
+
####Netsuite.com
31
31
- accounts
32
32
- accounting_periods
33
33
- accounting_books
@@ -47,7 +47,7 @@ To use this dbt package, you must have At least either one Fivetran **Netsuite**
47
47
- vendors
48
48
- vendor_types
49
49
50
-
### Netsuite2
50
+
####Netsuite2
51
51
- account
52
52
- accounttype
53
53
- accountingbooksubsidiary
@@ -72,18 +72,18 @@ To use this dbt package, you must have At least either one Fivetran **Netsuite**
72
72
- vendor
73
73
- vendorcategory
74
74
75
-
### Database Compatibility
75
+
####Database Compatibility
76
76
This package is compatible with either a **BigQuery**, **Snowflake**, **Redshift**, **PostgreSQL**, or **Databricks** destination.
77
77
78
-
### Databricks dispatch configuration
78
+
####Databricks dispatch configuration
79
79
If you are using a Databricks destination with this package, you must add the following (or a variation of the following) 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.
80
80
```yml
81
81
dispatch:
82
82
- macro_namespace: dbt_utils
83
83
search_order: ['spark_utils', 'dbt_utils']
84
84
```
85
85
86
-
## Step 2: Install the package (skip if also using the `Netsuite` transformation package)
86
+
### Step 2: Install the package (skip if also using the `Netsuite` transformation package)
87
87
If you are **not** using the [Netsuite transformation package](https://github.com/fivetran/dbt_netsuite), include the following package version in your `packages.yml` file. If you are installing the transform package, the source package is automatically installed as a dependency.
88
88
> TIP: 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.
89
89
```yaml
@@ -92,14 +92,14 @@ packages:
92
92
version: [">=0.10.0", "<0.11.0"]
93
93
```
94
94
95
-
## Step 3: Define Netsuite.com or Netsuite2 Source
95
+
### Step 3: Define Netsuite.com or Netsuite2 Source
96
96
As of April 2022 Fivetran made available a new Netsuite connector which leverages the Netsuite2 endpoint opposed to the original Netsuite.com endpoint. This package is designed to run for either or, not both. By default the `netsuite_data_model` variable for this package is set to the original `netsuite` value which runs the netsuite.com version of the package. If you would like to run the package on Netsuite2 data, you may adjust the `netsuite_data_model` variable to run the `netsuite2` version of the package.
97
97
```yml
98
98
vars:
99
99
netsuite_data_model: netsuite2 #netsuite by default
100
100
```
101
101
102
-
## Step 4: Define database and schema variables
102
+
### Step 4: Define database and schema variables
103
103
By default, this package runs using your destination and the `netsuite` schema. If this is not where your Netsuite data is (for example, if your netsuite schema is named `netsuite_fivetran`), add the following configuration to your root `dbt_project.yml` file:
104
104
105
105
```yml
@@ -108,7 +108,7 @@ vars:
108
108
netsuite_schema: your_schema_name
109
109
```
110
110
111
-
## Step 5: Disable models for non-existent sources (Netsuite2 only)
111
+
### Step 5: Disable models for non-existent sources (Netsuite2 only)
112
112
It's possible that your Netsuite connector does not sync every table that this package expects. If your syncs exclude certain tables, it is because you either don't use that feature in Netsuite or actively excluded some tables from your syncs. To disable the corresponding functionality in the package, you must add the relevant variables. By default, all variables are assumed to be true. Add variables for only the tables you would like to disable:
113
113
```yml
114
114
vars:
@@ -118,14 +118,14 @@ vars:
118
118
netsuite2__using_jobs: false # True by default. Disable `job` if you don't use jobs
119
119
120
120
```
121
-
> **Note**: The Netsuite dbt package currently only supports disabling transforms of [Multi-Book Accounting](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/book_3831565332.html) related tables (`accountingbooksubsidiary` and `accountingbook`), the `vendorcategory` source table, and the `job` source table. Please create an issue to request additional tables and/or [features](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/bridgehead_N233872.html) to exclude.
122
-
>
121
+
> **Note**: The Netsuite dbt package currently only supports disabling transforms of [Multi-Book Accounting](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/book_3831565332.html) related tables (`accountingbooksubsidiary` and `accountingbook`), the `vendorcategory` source table, and the `job` source table. Please create an issue to request additional tables and/or [features](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/bridgehead_N233872.html) to exclude.
122
+
>
123
123
> To determine if a table or field is activated by a feature, access the [Records Catalog](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/article_159367781370.html).
124
124
125
-
## (Optional) Step 6: Additional configurations
125
+
###(Optional) Step 6: Additional configurations
126
126
<details><summary>Expand for configurations</summary>
127
127
128
-
### Passing Through Additional Fields
128
+
####Passing Through Additional Fields
129
129
This package includes all source columns defined in the macros folder. You can add more columns using our pass-through column variables. These variables allow for the pass-through fields 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:
130
130
131
131
```yml
@@ -165,7 +165,7 @@ vars:
165
165
- name: "items_custom_field"
166
166
alias: "items_field"
167
167
```
168
-
### Change the build schema
168
+
#### Change the build schema
169
169
By default, this package builds the Netsuite staging models within a schema titled (`<target_schema>` + `_netsuite_source`) in your destination. If this is not where you would like your netsuite staging data to be written to, add the following configuration to your root `dbt_project.yml` file:
170
170
171
171
```yml
@@ -174,7 +174,7 @@ models:
174
174
+schema: my_new_schema_name # leave blank for just the target_schema
175
175
```
176
176
177
-
### Change the source table references
177
+
#### Change the source table references
178
178
If an individual source table has a different name than the package expects, add the table name as it appears in your destination to the respective variable:
179
179
> IMPORTANT: See this project's [`dbt_project.yml`](https://github.com/fivetran/dbt_netsuite_source/blob/main/dbt_project.yml) variable declarations to see the expected names.
This package is designed to run **either** the Netsuite.com or Netsuite2 data models. However, for documentation purposes, an additional variable `netsuite_data_model_override` was created to allow for both data model types to be run at the same time by setting the variable value to `netsuite`. This is only to ensure the [dbt docs](https://fivetran.github.io/dbt_netsuite_source/) (which is hosted on this repository) is generated for both model types. While this variable is provided, we recommend you do not adjust the variable and instead change the `netsuite_data_model` variable to fit your configuration needs.
191
191
192
192
</details>
193
193
194
-
## (Optional) Step 7: Orchestrate your models with Fivetran Transformations for dbt Core™
194
+
### (Optional) Step 7: Orchestrate your models with Fivetran Transformations for dbt Core™
195
195
<details><summary>Expand for details</summary>
196
196
<br>
197
197
198
198
Fivetran offers the ability for you to orchestrate your dbt project through [Fivetran Transformations for dbt Core™](https://fivetran.com/docs/transformations/dbt). Learn how to set up your project for orchestration through Fivetran in our [Transformations for dbt Core™ setup guides](https://fivetran.com/docs/transformations/dbt#setupguide).
199
199
200
200
</details>
201
201
202
-
# 🔍 Does this package have dependencies?
203
-
This dbt package is dependent on the following dbt packages. Please be aware that these dependencies are installed by default within this package. For more information on the following packages, refer to the [dbt hub](https://hub.getdbt.com/) site.
202
+
## Does this package have dependencies?
203
+
This dbt package is dependent on the following dbt packages. These dependencies are installed by default within this package. For more information on the following packages, refer to the [dbt hub](https://hub.getdbt.com/) site.
204
204
> IMPORTANT: If you have any of these dependent packages in your own `packages.yml` file, we highly recommend that you remove them from your root `packages.yml` to avoid package version conflicts.
205
205
```yml
206
206
packages:
@@ -214,15 +214,15 @@ packages:
214
214
version: [">=0.3.0", "<0.4.0"]
215
215
```
216
216
217
-
# 🙌 How is this package maintained and can I contribute?
218
-
## Package Maintenance
217
+
## How is this package maintained and can I contribute?
218
+
### Package Maintenance
219
219
The Fivetran team maintaining this package _only_ maintains the latest version of the package. We highly recommend that you stay consistent with the [latest version](https://hub.getdbt.com/fivetran/netsuite_source/latest/) of the package and refer to the [CHANGELOG](https://github.com/fivetran/dbt_netsuite_source/blob/main/CHANGELOG.md) and release notes for more information on changes across versions.
220
220
221
-
## Contributions
222
-
A small team of analytics engineers at Fivetran develops these dbt packages. However, the packages are made better by community contributions!
221
+
### Contributions
222
+
A small team of analytics engineers at Fivetran develops these dbt packages. However, the packages are made better by community contributions.
223
223
224
-
We highly encourage and welcome contributions to this package. Check out [this dbt Discourse article](https://discourse.getdbt.com/t/contributing-to-a-dbt-package/657) to learn how to contribute to a dbt package!
224
+
We highly encourage and welcome contributions to this package. Check out [this dbt Discourse article](https://discourse.getdbt.com/t/contributing-to-a-dbt-package/657) to learn how to contribute to a dbt package.
225
225
226
-
# 🏪 Are there any resources available?
227
-
- If you have questions or want to reach out for help, please refer to the [GitHub Issue](https://github.com/fivetran/dbt_netsuite_source/issues/new/choose) section to find the right avenue of support for you.
226
+
## Are there any resources available?
227
+
- If you have questions or want to reach out for help, see the [GitHub Issue](https://github.com/fivetran/dbt_netsuite_source/issues/new/choose) section to find the right avenue of support for you.
228
228
- If you would like to provide feedback to the dbt package team at Fivetran or would like to request a new dbt package, fill out our [Feedback Form](https://www.surveymonkey.com/r/DQ7K7WW).
0 commit comments