# Script JSON Format

**URL:** <https://forum.inductiveautomation.com/t/script-json-format/90434>\
**Category:** Ignition\
**Created:** [May 15, 2024, 2:00pm UTC](https://forum.inductiveautomation.com/t/script-json-format/90434 "2024-05-15T14:00:27Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 15, 2024, 2:37pm UTC](https://forum.inductiveautomation.com/t/script-json-format/90434/5 "2024-05-15T14:37:01Z")

</div>

I do think IA should route all JSONification through instances of `TreeMap` with a human- and source-control-friendly case-sensitive [alphanumeric comparator](https://files.inductiveautomation.com/sdk/javadoc/ignition81/8.1.38/com/inductiveautomation/ignition/common/util/Comparators.html) for the keys. Perhaps with an performance exception for payloads going straight to the browser.

Especially including [system.util.jsonEncode()](https://www.docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-util/system-util-jsonEncode). So that all json that ends up on disk (including json from document or other tags) is **deterministic**.

The JSON spec may not care about key order, but lots of other dependent functionality **does**.

---

_[View the full topic](https://forum.inductiveautomation.com/t/script-json-format/90434)._