Perspective 8.3.3 – Indirect Binding Not Updating in Real Time in Nested Template

General Discussion
, ,
1

Perspective 8.3.3 – Indirect Binding Not Updating in Real Time in Nested Template

Hi everyone,

I am facing an issue with Indirect Binding in Ignition Perspective 8.3.3 and would appreciate any guidance.

I have the following structure in my project:

Popup → Template → Template containing Table

The popup is opened from a Label/Template, and I pass a tag path as a parameter to the popup.

Inside the popup, I am calling another reusable template/view which contains a Table. The table data is generated using Indirect Binding based on the tag path/parameter passed to the popup.

Issue

The indirect binding works correctly when the popup is initially opened. However, the values displayed in the table are not updating in real time when the underlying tag values change.

For example:

  1. Open the popup.

  2. The table displays the current tag value correctly.

  3. The PLC/tag value changes.

  4. The value in the table does not update.

  5. If I close the popup and open it again, the latest value is displayed correctly.

So it appears that the indirect binding is resolving the tag path initially, but the binding is not maintaining the expected realtime subscription/update after the popup is opened.

Additional Information

  • Ignition Perspective version: 8.3.3

  • The popup contains a reusable template/view.

  • That template contains a Table component.

  • The table uses Indirect Binding.

  • The tag path is passed dynamically through view/template parameters.

  • The initial value is correct.

  • The problem is specifically with realtime updates.

  • Closing and reopening the popup causes the latest value to appear.

Has anyone experienced a similar issue with Indirect Binding inside nested templates/views in a Perspective popup?

Is there anything specific I need to do to ensure that the indirect binding maintains its realtime subscription when the parameter/tag path is passed dynamically?

Any suggestions regarding the correct binding structure or recommended approach would be appreciated.

Thank you!

2

Show your actual binding configuration for the items in question, via screenshot or code snippet or both.

Based on the behavior it sounds like you might be passing only the tag value through to one of the levels without realizing, but it could possibly be how the table is handling embedded views.

Also show however your table is configured, again to help verify that it is a component/Ignition problem and not a user configuration problem.

Additionally, you can attempt troubleshooting by providing a valid parameter value in the designer to the views in question to validate they are working as expected at the various levels.