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
There are a few fields that are explicitly dates in Netsuite2 according to the Records Catalog. However, these get converted to timestamps in the connector due to Netsuite's metadata calling these date fields instants
Affected fields based on this code search and the Records Catalog data type:
transactions.trandate
transactions.duedate
transactions.closedate
customers.firstOrderDate
accountingperiods.startdate
accountingperiods.enddate
accountingperiods.closedOnDate
the following fields come up in the code search but are confirmed true datetimes (so don't change these):
transactions.closedOnDate
vendors.datecreated
For the relevant fields, we should
Cast them as dates in the staging models (before doing so will we need to convert timezones?)
(probably) change their aliases from *_at to *_on or *_date. This would be a breaking change though!!!!
Describe alternatives you've considered
No response
Are you interested in contributing this feature?
Yes.
Yes, but I will need assistance and will schedule time during your office hours for guidance.
Is there an existing feature request for this?
Describe the Feature
There are a few fields that are explicitly
dates
in Netsuite2 according to the Records Catalog. However, these get converted to timestamps in the connector due to Netsuite's metadata calling these date fieldsinstants
Affected fields based on this code search and the Records Catalog data type:
the following fields come up in the code search but are confirmed true
datetimes
(so don't change these):For the relevant fields, we should
*_at
to*_on
or*_date
. This would be a breaking change though!!!!Describe alternatives you've considered
No response
Are you interested in contributing this feature?
Anything else?
originated from https://getdbt.slack.com/archives/C01D1R2JLLA/p1709549154256589
The text was updated successfully, but these errors were encountered: