this was driving me crazy in a much more complex flex repeater + instance, but here is the most simplest , reproducible example:
There is a Parent view with flex repeater. the flex repeater instance passes a parameter “id” to the child view. instances is just static data, it doesnt change.
The child view has a binding on the view.params.id .The binding also prints to console that it fired and the id number.
As you can see in the console in the screenshot every time this parent view starts up, in each child the binding fires 2x. the same result shows in the designer and the browser.
This is driving me a bit crazy in particular if I want to have a tag history binding on the child view, and its firing multiple times per instance, putting more load on the server/database than necessary. I already tried having the tag history query on the parent, but this is not ideal, I dont want users to wait to see the rest of the child view while tag history data is fetching.
I tested this with the same result on 8.1.44 and 8.3.2-rc2
here is the two views if you want to check:
flex repeater bug.zip (14.4 KB)