-
Notifications
You must be signed in to change notification settings - Fork 22
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
[Bug] ERRORS ON TRANSFORMATIONS #45
Comments
please understand that I don't know coding, and I don't understand why a service that I pay for expects me as the end user to make a github account and speak programming lingo to programmers to get a problem solved that's affecting my business. I'm stressing my balls off here, for the love of God please help. |
Hi @zdrag, as a member of the team responsible for developing our data models, I want to say thanks for bringing this issue to our attention. I understand the frustration and inconvenience it has caused you and your business. It's important for us to address issues like this, so your feedback helps us ensure that everything functions as expected. Regarding the leap year issue, we've identified a potential fix to calculate the last day of the month instead of relying on the column We're actively working on resolving this issue, and I'll keep you updated on our progress. |
Hi @zdrag, to update you on our approach, we confirmed that I wanted to check in with you to see if you have any objections or concerns regarding this solution. If not, we'll proceed with releasing the fix. |
Hi @fivetran-catfritz that's perfect - thank you, should resolve the problem as leap-years are only every 4 years. Regards |
Great, and thank you for taking a look @zdrag. My team's code updates have been approved and released; therefore, I will be closing this Issue. Now it's a matter of the Fivetran Quickstart product being updated with those changes. For this next step, you can follow up with your Support ticket to receive status updates on when this will be live in Quickstart. |
Is there an existing issue for this?
Describe the issue
This pertains to Xero Balance Sheet transformations.
Notice how you use the snapshot financial_year_end_month and financial_year_end_day as the financial year end, so it goes and creates the 29th of February for 2023, 2022, 2021 etc.
Those dates don't exist and create an error:
I've attached the file showing financial_year_end_day and financial_year_end_month as fixed on 02/29.
Relevant error log or model output
Expected behavior
Not to give an error
dbt Project configurations
I don't know how to do this, I'm not a programmer
Package versions
I don't know how to do this, I'm not a programmer
What database are you using dbt with?
snowflake
dbt Version
I don't know how to do this, I'm not a programmer
Additional Context
I'm being sent here by fivetran support, as a business user who does ACCOUNTING, instead of FIvetran handling it. My whole system is offline because of the errors and Fivetran can't give two shits about that.
Are you willing to open a PR to help address this issue?
The text was updated successfully, but these errors were encountered: