Skip to content

Simplify prune-scope mode documentation and fix example #97

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.

Sign up for GitHub

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

Merged
karlrank merged 1 commit into from
Feb 10, 2026
Merged

Simplify prune-scope mode documentation and fix example #97

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 2 additions & 3 deletions docs/integrations/inbound/mapping.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -305,8 +305,7 @@ When using prune-scope modes, you must provide a `scope` configuration that defi

| Mode | Description |
|------|-------------|
| `relations` | Find scope by looking at what a specific entity relates TO |
| `reverse-relations` | Find scope by looking at what's related TO a specific entity |
| `relations` | Find scope by looking at all entities related to a specific entity (both direct and reverse relations) |
| `query` | Find scope entities directly via query parameters |

#### Example: Sync Billing Events for a Billing Account
Expand All @@ -322,7 +321,7 @@ When receiving a billing account update with billing events, sync all billing ev
"jsonataExpression": "$map(billingevents[], function($v) { $merge([$v, { \"billingaccountnumber\": billingaccountnumber }]) })",
"mode": "upsert-prune-scope-purge",
"scope": {
"scope_mode": "reverse-relations",
"scope_mode": "relations",
"schema": "billing_account",
"unique_ids": [
{
Expand Down
Loading