# 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:** 18

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [September 25, 2025, 6:22am UTC](https://forum.inductiveautomation.com/t/flex-repeater-instances-sometimes-initialize-null-values-embedded-view/92867/18 "2025-09-25T06:22:09Z")

</div>

I've come up against this again in 8.1.49. From what I can tell with my limited testing, is that it only affects Views' params that are complex types. I haven't tested arrays, but objects (dicts) are certainly affected. As soon as I start using keys directly in the `params` object, I don't have any issues with these.

In my case, I'm seeing an issue with only 2 layers of embedding when using complex params types. I.e.  
Main View (this is the view linked to a page url) -\> Embebbed View (motor symbol) -\> Embedded View (alarm symbol) [this embedded view isn't always receiving the param values from the motor symbol like `params.alarmSummary.tagPath`]

So the workaround, at least from my minimal testing, seems to be:

- don't use complex params types such as `object` and `array`  
e.g. _don't use_ `params.alarmSummary.tagPath`
- do use `value` type keys directly within the `params` object  
e.g. _do use_ `params.alarmSummary_tagPath`

---

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