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

Update dot notation support #7363

Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions src/connections/destinations/actions.md
Original file line number Diff line number Diff line change
Expand Up @@ -222,6 +222,7 @@ Mapping fields are case-sensitive. The following type filters and operators are
You can specify nested properties using dot notation, for example `context.app.name`. If the property might appear in more than one format or location, you can use an ANY statement and add conditions for each of those formats. For example, you might filter for both `context.device.type = ios` as well as `context.os.name = "iPhone OS``"`
The `does` `not exist` operator matches both a `null` value or a missing property.
{% comment %}
However, ou cannot specify properties that are nested within an array. For example, this notation - `products[0].category` - would not yield any results.

> info "Valid property and trait values"
> Property and trait names must begin with the characters: [a-z], [A-Z] or '_'. Property and trait names don't support special characters in the first character. If you save a property or trait with a special character in the first character, you'll get an Invalid Trigger error.
Expand Down Expand Up @@ -250,9 +251,6 @@ You can combine criteria in a single group using **ALL** or **ANY**. Use an ANY
> info "Unsupported Special Characters"
> Mappings do not support the use of double quotes " or a tilde ~ in the trigger fields. In mapping fields, the . character is not supported unless it's being used to access an object key. If a string has a . in it, that is not supported.

> info "Limitations"
> Mapping fields don't support dot notation. For example, properties.amount.cost or properties_amount.cost aren't supported.

> info "Destination Filters"
> Destination filters are compatible with Destination Actions. Consider a Destination Filter when:
> - You need to remove properties from the data sent to the destination
Expand Down