# Project creation automation strategies **URL:** \ **Category:** Ignition\ **Created:** [April 25, 2026, 7:55pm UTC](https://forum.inductiveautomation.com/t/project-creation-automation-strategies/115255 "2026-04-25T19:55:07Z")\ **Posts on this page:** 1\ **Showing post:** 16
**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\ **Post date:** [April 28, 2026, 2:42pm UTC](https://forum.inductiveautomation.com/t/project-creation-automation-strategies/115255/16 "2026-04-28T14:42:04Z")
It’s been a pretty stable component, I’d love to hear your feedback. One of the big advantages of the JSON View component is dynamic bindings. The biggest issue at the moment is that the `view.json` schema, while valid JSON, can contain keys that are not allowed in the Property Tree. See this thread: > [@Perspective special characters in property names / object keys](https://forum.inductiveautomation.com/t/perspective-special-characters-in-property-names-object-keys/114943/5): > > I would also appreciate the ability to use arbitrary strings as property keys. With the expectation that if I have a key that is not supported via the dot accessor syntax, that I’ll need to use square bracket notation or a getter: # Python string = `{ "key": "value", "20": "key of numeric string", "prop.test": "key with a period" }` obj = system.util.jsonDecode(string) print obj["20"] # key of numeric string print obj["prop.test"] # key with a period // JavaScript const string = `{ … If you’re loading the view definition from a script/binding, you can get the Property Tree to take the values. If you’re editing it by hand though it will reject the writes. --- _[View the full topic](https://forum.inductiveautomation.com/t/project-creation-automation-strategies/115255)._