Skip to content

Commit 7b53ad9

Browse files
Update actions.md
1 parent 1543fd7 commit 7b53ad9

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/connections/destinations/actions.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -261,11 +261,11 @@ The available operators depend on the property's data type:
261261

262262
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.
263263

264-
> info "Unsupported Special Characters"
265-
> 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.
264+
> info "Unsupported Special Characters In Trigger Fields"
265+
> Trigger fields do not support the use of double quotes `"` or a tilde `~`.
266266
267-
> info "Limitations"
268-
> Mapping fields don't support dot notation. For example, properties.amount.cost or properties_amount.cost aren't supported.
267+
> info "Mappings Limitations"
268+
> 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.
269269
270270
> info "Destination Filters"
271271
> Destination filters are compatible with Destination Actions. Consider a Destination Filter when:

0 commit comments

Comments
 (0)