# \[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:** 16

<div class="post-metadata">

**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\
**Post date:** [September 9, 2021, 2:48pm UTC](https://forum.inductiveautomation.com/t/bug-invalid-key-on-object-binding/45763/16 "2021-09-09T14:48:06Z")

</div>

> [@victordcq](#):
>
> welh using spaces and numbers makes it harder to use `this.props.data.data field` but you can still do `this.props.data['data field']`

My data is being used only for output in the table view. I don't actually need to reference it any other way, so the awkward keying doesn't affect me.

> [@pascal.fragnoud](#):
>
> I don’t know if that can apply to your situation, but I ended up ditching that system and using a list of objects of this sort:

I can't alter the basic structure since I have to match the expectations of the [Perspective table component](https://forum.inductiveautomation.com/t/feedback-new-perspective-table/21199). I did consider "mangling" the names in the data table, but I need them to display properly, so that would require I generate a dynamic `columns` property to map names for the user display.

---

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