Before you start
Confirm:- The saved run setup exists, with both source systems and primary ID fields chosen. If it does not, start with Set up a reconciliation run.
- Saved schemas exist for JSON sources, so the field paths you compare are known.
- You know which fields must line up between the two systems (for example price, quantity, or status).
- You are a Tenant Admin for the active tenant. Editing rules requires tenant edit access.
How a rule reads
A rule is a single field-to-field comparison:| Part | What it means |
|---|---|
| File 1 field | The field path selected from the first source. |
| Operator | The comparison applied between the two values. |
| File 2 field | The field path selected from the second source. |
| Pre-actions | Optional value conversions applied before comparison, per field side. |
Operators
The Ruleset Manager offers these comparison operators:| Operator | Passes when |
|---|---|
= | The two field values are equal. |
!= | The two field values are not equal. |
> | The file 1 value is greater than the file 2 value. |
< | The file 1 value is less than the file 2 value. |
>= | The file 1 value is greater than or equal to the file 2 value. |
<= | The file 1 value is less than or equal to the file 2 value. |
Pre-actions
Pre-actions normalize a field value before the operator runs, so a comparison is not defeated by source formatting. Each pre-action applies to one field side.| Pre-action | Use it for |
|---|---|
| String to int | Comparing whole-number fields stored as text. |
| String to number | Comparing decimal fields stored as text. |
Steps
Open the Ruleset Manager
Open Ask Darpan with
Cmd/Ctrl+K or the floating Ask Darpan button. Choose Open Runs Settings (or search the saved run by name), then open the run you are configuring; ruleset-type runs open in the Ruleset Manager.The Ruleset Manager shows the two compared sources, their schemas, and the current list of rules.Open the rule editor
In the Rules section, choose Edit Rules. This opens the rule editor, where each rule appears in sequence as a file 1 field, an operator, and a file 2 field.
Add or edit a rule
To add a rule, connect a field from the first source to its matching field on the second source: press and drag from one field pill to the other to draw a line between them. To edit an existing rule, select its operator box.In the rule popover that opens, choose the Operator. Pre-actions and the sequence number are set here too.Pick fields that should always line up when the two systems are in sync. A price field on one side maps to the price field on the other; a quantity to a quantity.
Add pre-actions when formats differ
When one side stores a value as text and the other as a number, add a Pre Action on the affected field side so the values compare correctly. Use String to int for whole numbers and String to number for decimals.
Save the rule
Choose Save rule. The rule joins the active comparison and is included in the next run.
Expected result
The saved run now carries an explicit RuleSet. The next time the run executes, Darpan matches records by primary ID, applies the RuleSet to each matched pair, and records a difference whenever a rule fails. Those differences are what you review and what drives run-completion alerts.After authoring
- Run the saved setup once and review the output to confirm rules flag the right differences. See Run reconciliation and Review results.
- Turn on run-completion alerts so failures surface without manual checking. See Run-completion alerts.
- Schedule the run when the same comparison should repeat. See Set up an automation.