Record Key Value Transposer
Transpose own object members to ordered key/value entry records without flattening nested values.
Description
Transpose own object members to ordered key/value entry records without flattening nested values.
An object's members can be represented as explicit key/value records. That representation preserves keys as data when passing the contents to a table or record-processing step.
When to use this tool
Transpose own object members to ordered key/value entry records without flattening nested values.
- Prepare the supplied objectJson 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 objectJson. 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.entries. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require objectJson to decode to an object, enumerate its own entries, and return one {key,value} record per member without changing the values.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| objectJson | 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": "objectJson",
"decoded": {
"a": 1,
"b": null
}
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.entries | The entries list in the ordering and representation described above. |
{
"input": {
"objectJson": "{\"a\":1,\"b\":null}"
},
"output": {
"result": {
"entries": [
{
"key": "a",
"value": 1
},
{
"key": "b",
"value": null
}
]
}
}
}Limitations and assumptions
- This is a shallow conversion. JavaScript property enumeration determines row order, including its handling of integer-like keys; nested objects are retained as values.
- Decoded JSON is bounded to 20,000 nodes and 32 nesting levels; record arrays have at most 128 records. Parsed number values use JavaScript floating point rather than arbitrary-precision decimal arithmetic.
- 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.
- Ordinary string lists have at most 128 entries of at most 128 code units each; numeric lists and matrices have separate bounded size checks. Nonfinite results and excessively large serialized outputs are rejected.
- 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
For document-wide requirements, combine these structural inventories with an explicit JSON Schema. Preserve the distinction between missing properties and null values, and between numbers and numeric-looking strings when building joins or indexes.
References
Similar or alternative tools
- Record Foreign Key Coverage Table
Audit typed-scalar foreign-key coverage against an explicit reference inventory; absent and unmatched values remain distinct.
- Record Key Multiplicity Audit
Audit typed-scalar record key multiplicities while retaining missing-key records and duplicate positions.