# How many views deep can you go before parameters have issues passing?

**URL:** <https://forum.inductiveautomation.com/t/how-many-views-deep-can-you-go-before-parameters-have-issues-passing/93699>\
**Category:** Ignition\
**Tags:** perspective, ignition81\
**Created:** [July 24, 2024, 7:31pm UTC](https://forum.inductiveautomation.com/t/how-many-views-deep-can-you-go-before-parameters-have-issues-passing/93699 "2024-07-24T19:31:09Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Louis\_Whitburn](https://avatars.discourse-cdn.com/v4/letter/l/8baadc/32.png) [@Louis\_Whitburn](https://forum.inductiveautomation.com/u/Louis_Whitburn)\
**Post date:** [July 25, 2024, 2:05am UTC](https://forum.inductiveautomation.com/t/how-many-views-deep-can-you-go-before-parameters-have-issues-passing/93699/12 "2024-07-25T02:05:21Z")

</div>

We've hit this issue (or something related) a few times. Despite IA Support saying that is is triggered by a 'race condition' I don't know if they've ever confirmed that it's a bug (even though I'd consider any race condition to be a bug).  
One thing I've found to _potentially_ help is making sure 'persistent' is disabled on any of the properties which have the problematic bindings. It looks like someone else on the forum has a similar suggestion: [Flex Repeater instances sometimes initialize null values (embedded view) - #14 by rpavlicek](https://forum.inductiveautomation.com/t/flex-repeater-instances-sometimes-initialize-null-values-embedded-view/92867/14)

---

_[View the full topic](https://forum.inductiveautomation.com/t/how-many-views-deep-can-you-go-before-parameters-have-issues-passing/93699)._
