-
Notifications
You must be signed in to change notification settings - Fork 7
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.
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/gl batch addition #19
Conversation
packages.yml
Outdated
# version: [">=0.3.0", "<0.4.0"] | ||
|
||
- git: https://github.com/fivetran/dbt_sage_intacct_source.git | ||
revision: feature/gl-batch-addition | ||
warn-unpinned: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be switched before merge
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ran and tested locally. Just one small suggestion in the changelog, but otherwise lgtm!
|
||
## Under the Hood | ||
- Updated Maintainer PR Template | ||
- Included auto-releaser GitHub Actions workflow to automate future releases |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😃
CHANGELOG.md
Outdated
- Removal of the `_fivetran_deleted` field from the upstream `stg_sage_intacct__gl_detail` table due to this field being deprecated within the connector. The relevant information is now available within the `gl_batch` source table. For more details please refer to the relevant [dbt_sage_intacct_source v0.3.0 release](https://github.com/fivetran/dbt_sage_intacct_source/releases/tag/v0.3.0). | ||
|
||
## Bug Fixes | ||
- Added a new `int_sage_intacct__active_gl_detail` model. This model properly filters out any soft deleted GL Detail records by joining on the GL Batch staging model which contains the reference to if the transaction was deleted or not. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As you mentioned in the validation, might want to mention that this could result in removed rows from downstream models.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure thing! Added.
|
||
## Bug Fixes | ||
- Added a new `int_sage_intacct__active_gl_detail` model. This model properly filters out any soft deleted GL Detail records by joining on the GL Batch staging model which contains the reference to if the transaction was deleted or not. | ||
- While this package still does not fully support multi-currency, a bugfix was applied in the `int_sage_intacct__general_ledger_balances` model to properly join on the `currency` field so duplicates would not be introduced in the end models. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A rather impactful find!
PR Overview
This PR will address the following Issue/Feature: Issue #13
This PR will result in the following new package version:
v0.3.0
While this is not necessarily breaking, the upstream change in the source package is. Therefore, this should be recorded as a breaking change.
Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:
🚨 Breaking Changes 🚨 (within the upstream dbt_sage_intacct_source package):
_fivetran_deleted
field from the upstreamstg_sage_intacct__gl_detail
table due to this field being deprecated within the connector. The relevant information is now available within thegl_batch
source table. For more details please refer to the relevant dbt_sage_intacct_source v0.3.0 release.Bug Fixes
int_sage_intacct__active_gl_detail
model. This model properly filters out any soft deleted GL Detail records by joining on the GL Batch staging model which contains the reference to if the transaction was deleted or not.int_sage_intacct__general_ledger_balances
model to properly join on thecurrency
field so duplicates would not be introduced in the end models.currency
into consideration:sage_intacct__general_ledger_by_period
sage_intacct__profit_and_loss
sage_intacct__balance_sheet
Under the Hood
PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:
Before marking this PR as "ready for review" the following have been applied:
Detailed Validation
Please share any and all of your validation steps:
All validations were performed within the Sage Intacct Validations Hex workbook. Please refer to the Height ticket for a direct link to these validations. The Hex notebook includes the following validations:
If you had to summarize this PR in an emoji, which would it be?
🌽