# Flex Repeater instances sometimes initialize null values (embedded view)

**URL:** <https://forum.inductiveautomation.com/t/flex-repeater-instances-sometimes-initialize-null-values-embedded-view/92867>\
**Category:** Ignition\
**Tags:** perspective, ignition81\
**Created:** [July 7, 2024, 4:09pm UTC](https://forum.inductiveautomation.com/t/flex-repeater-instances-sometimes-initialize-null-values-embedded-view/92867 "2024-07-07T16:09:36Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![rpavlicek](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/rpavlicek/32/55868_2.png) [@rpavlicek](https://forum.inductiveautomation.com/u/rpavlicek)\
**Post date:** [July 9, 2024, 5:17pm UTC](https://forum.inductiveautomation.com/t/flex-repeater-instances-sometimes-initialize-null-values-embedded-view/92867/14 "2024-07-09T17:17:27Z")

</div>

I do have a very dynamic and flexible central view going on. Of what you mentioned, its always on the back of my mind to not get too complex and know when to scale back. Obviously, making use of style classes can handle central styling and such, but I also have properties that look at alarm states and some other things that give it much more power all from one spot.  
I'm going to look at other alternatives for the one binding I have that may be triggering all of this.

---

_[View the full topic](https://forum.inductiveautomation.com/t/flex-repeater-instances-sometimes-initialize-null-values-embedded-view/92867)._