Key Value Block Duplicate Audit
Audit duplicate literal keys in an ordered key-value block without choosing first or last wins.
Description
Audit duplicate literal keys in an ordered key-value block without choosing first or last wins.
Repeated key/value entries can be audited without collapsing them into one dictionary.
When to use this tool
Audit duplicate literal keys in an ordered key-value block without choosing first or last wins.
- Prepare the supplied pairsJson fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter pairsJson. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.duplicates. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Parse pairsJson as exactly two-string arrays. Group by the first string and return duplicate keys with every pair index.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| pairsJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
For the JSON text fields, the following decoded structures show the example records before they are serialized into input strings. Keep field names, list nesting and value types as shown.
[
{
"field": "pairsJson",
"decoded": [
[
"a",
"1"
],
[
"b",
"2"
],
[
"a",
"3"
]
]
}
] | Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.duplicates | The duplicates list in the ordering and representation described above. |
{
"input": {
"pairsJson": "[[\"a\",\"1\"],[\"b\",\"2\"],[\"a\",\"3\"]]"
},
"output": {
"result": {
"duplicates": [
{
"key": "a",
"indexes": [
0,
2
]
}
]
}
}
} Limitations and assumptions
- Values do not affect grouping. No first-wins, last-wins, trimming or case normalization is applied.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Choose the exact text grammar before combining serializers and parsers. UTF-16 record lengths, raw separators and custom backslash escapes differ from byte framing, CSV, Markdown and spreadsheet semantics.
References
Similar or alternative tools
- Literal Key Value Line Formatter
Format a literal name-value line while rejecting delimiters inside its name to retain first-split reversibility.
- Literal Key Value Line Parser
Split one literal name-value line at its first caller delimiter; does not trim, unquote or interpret escapes.