From cff99852b4d043086c5ab0a7318948906ba2d540 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 10 Feb 2026 10:05:01 +0000 Subject: [PATCH] Remove reverse-relations scope mode, merge into relations The `reverse-relations` scope_mode has been consolidated into `relations`, which now handles both direct and reverse relations. Updated the scope_mode options table and the billing events example accordingly. https://claude.ai/code/session_019wJ6Y7yqkSciqAJAiEz9cJ --- docs/integrations/inbound/mapping.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/integrations/inbound/mapping.md b/docs/integrations/inbound/mapping.md index a632d5b..3447f75 100644 --- a/docs/integrations/inbound/mapping.md +++ b/docs/integrations/inbound/mapping.md @@ -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 @@ -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": [ {