# \[bug?\] Invalid key on object binding

**URL:** <https://forum.inductiveautomation.com/t/bug-invalid-key-on-object-binding/45763>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [April 19, 2021, 5:20pm UTC](https://forum.inductiveautomation.com/t/bug-invalid-key-on-object-binding/45763 "2021-04-19T17:20:36Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [April 19, 2021, 9:02pm UTC](https://forum.inductiveautomation.com/t/bug-invalid-key-on-object-binding/45763/11 "2021-04-19T21:02:56Z")

</div>

I think it’s mostly just the json tree being overzealous with the warning, actually. From what I can tell, the type is preserved as a string pretty well throughout. If you don’t care about the warnings in the editor, it’s probably _reasonably_ safe to ignore…although I would still consider if there’s a different way to do things.

For instance, I set up a simple transform to return a dictionary with numeric strings as keys, and tested the type:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/8/18abb1caff41989d499c55a205360e7ab61d6513.png)

---

_[View the full topic](https://forum.inductiveautomation.com/t/bug-invalid-key-on-object-binding/45763)._