From 7b53ad93baf7ebede0cbace7fe8b0eb4ccd14029 Mon Sep 17 00:00:00 2001 From: "will.i.am" <110120307+wilwong-segment@users.noreply.github.com> Date: Wed, 11 Jun 2025 16:13:47 -0700 Subject: [PATCH 1/2] Update actions.md --- src/connections/destinations/actions.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md index a1e1906568..9eff8add0b 100644 --- a/src/connections/destinations/actions.md +++ b/src/connections/destinations/actions.md @@ -261,11 +261,11 @@ The available operators depend on the property's data type: You can combine criteria in a single group using **ALL** or **ANY**. Use an ANY to “subscribe” to multiple conditions. Use ALL when you need to filter for very specific conditions. You can only create one group condition per destination action. You cannot created nested conditions. -> 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 "Unsupported Special Characters In Trigger Fields" +> Trigger fields do not support the use of double quotes `"` or a tilde `~`. -> info "Limitations" -> Mapping fields don't support dot notation. For example, properties.amount.cost or properties_amount.cost aren't supported. +> info "Mappings Limitations" +> In mapping fields, the dot (`.`) character in destination fields is supported for creating nested objects and arrays (e.g., `info.name` or `info.[0].email`) unless enclosed in double quotes (e.g., `"user.email"` for a literal key). For source fields, dots are only supported for accessing object keys. Literal strings with dots in source property names are not supported. > info "Destination Filters" > Destination filters are compatible with Destination Actions. Consider a Destination Filter when: From 8da15eca9dec32c1e62df939c57d7d4c1d5a247a Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Wed, 11 Jun 2025 23:11:28 -0600 Subject: [PATCH 2/2] minor rewording --- src/connections/destinations/actions.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md index 9eff8add0b..66062e79d4 100644 --- a/src/connections/destinations/actions.md +++ b/src/connections/destinations/actions.md @@ -261,11 +261,11 @@ The available operators depend on the property's data type: You can combine criteria in a single group using **ALL** or **ANY**. Use an ANY to “subscribe” to multiple conditions. Use ALL when you need to filter for very specific conditions. You can only create one group condition per destination action. You cannot created nested conditions. -> info "Unsupported Special Characters In Trigger Fields" -> Trigger fields do not support the use of double quotes `"` or a tilde `~`. +> info "Unsupported special characters in trigger fields" +> Trigger fields don't support double quotes (`"`) or the tilde (`~`) character. -> info "Mappings Limitations" -> In mapping fields, the dot (`.`) character in destination fields is supported for creating nested objects and arrays (e.g., `info.name` or `info.[0].email`) unless enclosed in double quotes (e.g., `"user.email"` for a literal key). For source fields, dots are only supported for accessing object keys. Literal strings with dots in source property names are not supported. +> info "Mapping field limitations" +> In **destination** fields, you can use dot notation to create nested objects and arrays (for example, `info.name` or `info[0].email`), unless the field is enclosed in double quotes (for example, `"user.email"` creates a literal key, not a nested structure). In **source**, dots are only supported for accessing object keys. Literal strings that include a dot (like `user.email`) aren't supported as property names. > info "Destination Filters" > Destination filters are compatible with Destination Actions. Consider a Destination Filter when: