Skip to content
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

Incorrectly assigns time to date on CRM Opportunities #155

Open
lazjake opened this issue Oct 5, 2023 · 0 comments
Open

Incorrectly assigns time to date on CRM Opportunities #155

lazjake opened this issue Oct 5, 2023 · 0 comments

Comments

@lazjake
Copy link

lazjake commented Oct 5, 2023

The standard "list opportunities" API returns back a date string from the CRM: "close_date": "2023-05-26".

The node sdk opportunitiesAll returns it as datetime 2023-05-26T00:00:00.000Z.

In Salesforce, at least, Opportunity.CloseDate is only returned as a Date in the users current timezone, so treating it as UTC can make it fall on the wrong day.

Salesforce (and probably other CRMs) do store the UTC datetime somewhere, so the ideal case would be for Apideck to return that value. If not, the node sdk should just return the date and not datetime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant