# Any limitations on string or dictionary size in Ignition? **URL:** \ **Category:** Ignition\ **Tags:** ignition81, scripting\ **Created:** [November 16, 2022, 6:54pm UTC](https://forum.inductiveautomation.com/t/any-limitations-on-string-or-dictionary-size-in-ignition/66597 "2022-11-16T18:54:50Z")\ **Posts on this page:** 1\ **Showing post:** 12
**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 17, 2023, 9:18pm UTC](https://forum.inductiveautomation.com/t/any-limitations-on-string-or-dictionary-size-in-ignition/66597/12 "2023-05-17T21:18:03Z")
Look at the example for [system.util.jsonDecode](https://docs.inductiveautomation.com/display/DOC81/system.util.jsonDecode). Do that to assign to some top-level variable in a project script module. All usage elsewhere would be to `someScript.someVar[someKeyOrSubscript]`. Personally, I like running through such objects replacing dictionaries with my `SmartMap` subclass so that keys are accessible as properties: > [@Has anyone made an ORM work with Ignition transaction groups?](https://forum.inductiveautomation.com/t/has-anyone-made-an-orm-work-with-ignition-transaction-groups/64665/5): > > I've long been using a "SmartMap" extended dictionary that naturally allows property access to dictionary content. Create one with a tuple sequence of colName/colValue pairs and you suddenly have a very ORM-like row object. The one I like most delivers a None for missing keys automatically: #---------- # Handy tool for objects as "bags of properties" # by Peter Norvig, enhanced as a subclass of dict() by Philip J. Turmel # http://norvig.com/python-iaq.html class SmartMap(dict): def \_\_repr\_\_(… --- _[View the full topic](https://forum.inductiveautomation.com/t/any-limitations-on-string-or-dictionary-size-in-ignition/66597)._