Meta.name binding issue

Ignition
1

Hi All,

Embedded view shows its default param value when props.params.X is bound to this.meta.name
▎
▎ Ignition [8.3], Perspective Workstation. I have a template view (door lock) embedded a few hundred times across several screens. To save time, instead of typing in each instance's name param, I bound props.params.name → this.meta.name (property binding).
▎
▎ Occasionally, a few instances on a screen show the template's default name instead of their own.
▎
▎ It looks like the embedded view starts with its default params and sometimes never picks up the bound value, or keeps a stale one. Has anyone seen bound embedded-view params fail to update like this? Is binding to meta.name a known bad pattern? We're switching to typed-in params for now.

2

Please clarify: are you using meta.name as a source of a property binding? Or the destination of a property binding? (I would reconsider the latter--meta.name should be static.)

3

I am using meta.name as source

4

OK. I would expect it to work, so this might be a bug. There have been bugs in view parameter initialization, particularly when deeply nested, so this might be related. Consider opening a support ticket.

5

Yeah, jfan, this is a lingering bug in Perspective if you have too many layers of embedded views sometimes parameters don't initialize properly. You mention a few the views embedded hundred times across screens. What does the views typically look like?

Something like this will properly not work:
Door lock embedded in a door icon embedded in a building package embedded in an area view embedded in a site view

6

I want to clarify that I do not have any nested embedded views, and there is only one level. The view itself does exist in a global project, and I am launching it with a different project that inherits the view.

7

what I meant was the same template is being deployed in different screens, but not in different layers

8

Response from Inductive "They informed me that, with this particular binding, there is a chance that it will load as null, resulting in the listener capturing the null value before evaluation. In most cases, this can be fixed by ensuring that persistence is enabled for the binding. In our case, it was not enabled. Supporting evidence includes the fact that there are no issues with this binding during the initial load. As the Perspective application runs, however, the binding evaluation may fail."