[Bug] Timestamp not recognized error when generating datespine

[fivetran-joemarkiewicz]

Is there an existing issue for this?

• I have searched the existing issues

Describe the issue

In cases when there are no transactions yet in the General Ledger model the downstream datespine model will fail as there is not a minimum date to choose from. Thus results in the below provided error message.

To address this we will need to apply a coalesce to this model to ensure a date is specified even if there are no transactions in the General Ledger model. We have made similar updates to QuickBooks where we can apply a similar update to ensure users are able to see a successful run before transactions are seen in the General Ledger model.

Relevant error log or model output

database error in model int_sage_intacct__general_ledger_date_spine (models/intermediate/int_sage_intacct__general_ledger_date_spine.sql) 100035 (22007): timestamp 'none' is not recognized

Expected behavior

The models are able to succeed before transactions are available.

dbt Project configurations

Default

Package versions

v0.4.0

What database are you using dbt with?

snowflake

dbt Version

v1.8.1

Additional Context

No response

Are you willing to open a PR to help address this issue?

• Yes.
• Yes, but I will need assistance and will schedule time during our office hours for guidance
• No.

[fivetran-avinash]

Issue resolved in the above PR.