Updated FAQ section.md #6320
Merged
Updated FAQ section.md #6320
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Created the "Understanding HubSpot's `date` and dateTime` custom property types"
forstisabella
approved these changes
Apr 1, 2024
src/connections/destinations/catalog/actions-hubspot-cloud/index.md
Outdated
Show resolved
Hide resolved
src/connections/destinations/catalog/actions-hubspot-cloud/index.md
Outdated
Show resolved
Hide resolved
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created the "Understanding HubSpot's
dateand dateTime` custom property types"Proposed changes
Updated the FAQ and troubleshooting section with information on HubSpot's 'date' and 'dateTime' property types. Customers in the past have run into issues sending ISO 8601 formatted values to HubSpot because they unknowingly selected the incorrect 'date' property type in HubSpot for data containing a time value.
Merge timing
Related issues (optional)