Add section on Set Once/Set Always fields #5421
Merged
Conversation
This file contains hidden or 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
rchinn1
requested changes
Dec 4, 2023
src/connections/destinations/catalog/actions-amplitude/index.md
Outdated
Show resolved
Hide resolved
src/connections/destinations/catalog/actions-amplitude/index.md
Outdated
Show resolved
Hide resolved
src/connections/destinations/catalog/actions-amplitude/index.md
Outdated
Show resolved
Hide resolved
rchinn1
approved these changes
Dec 7, 2023
|
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.
Proposed changes
Amplitude's docs mention the following on user_properties operations:
"You can't mix user property operations with actual top-level user properties. Instead, include them inside the $set operation. If you are using one of these operators then this dictionary can contain only user property operations and you can't combine it with the above format. For example. you can't do {"$append":{"interests":"Music"}, "subscription type":"paid"} in the same request."
Add section to docs that calls out this limitation and how to circumnavigate it when using this destination.
Merge timing
Related issues (optional)