# \[Question\] Null values causing errors in Perspective

**URL:** <https://forum.inductiveautomation.com/t/question-null-values-causing-errors-in-perspective/23390>\
**Category:** Ignition Early Access\
**Created:** [March 15, 2019, 6:18pm UTC](https://forum.inductiveautomation.com/t/question-null-values-causing-errors-in-perspective/23390 "2019-03-15T18:18:06Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![grietveld](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/grietveld/32/6984_2.png) [@grietveld](https://forum.inductiveautomation.com/u/grietveld)\
**Post date:** [March 15, 2019, 8:21pm UTC](https://forum.inductiveautomation.com/t/question-null-values-causing-errors-in-perspective/23390/3 "2019-03-15T20:21:06Z")

</div>

They are bound to selectedRow properties in a table component. So they are really only null if no row has been selected yet they don’t have a value

I figure passing a one custom object bound to the points I need is easier than many individual bindings. (at least once that is fixed).

---

_[View the full topic](https://forum.inductiveautomation.com/t/question-null-values-causing-errors-in-perspective/23390)._