Troubleshoot nested layout content binding

What the symptoms point to

Use the visible behavior to choose your next check, not to declare the cause:

• The child layout appears, but its content pane stays blank: the container loaded. The inner pane may have no matching content, the wrong asset context, or a separate loading error.
• The pane works for some assets only: compare their content assignments, type values and access permissions.
• A direct, single-pane layout works, but the nested version does not: investigate context propagation and differences in pane settings.
• Neither the direct nor nested version works: check content selection and loading before changing the layout hierarchy.
• The previous asset's graphic remains after navigation: investigate refresh behavior and whether an earlier request can overwrite the current selection.
• Preview works but runtime does not: compare the selected asset, runtime account and navigation path. Preview may supply context that normal navigation does not.

An empty pane alone cannot distinguish a query with no result from content that was selected but failed to load.

Separate the container from the content lookup

Consider a parent layout containing a fixed reference to a child layout. Inside that child, another pane selects content using the current asset and a content type such as Overview.

There are two different questions:

1. Can the parent load the child layout by its fixed reference?
2. Can the child's pane resolve and load the requested content for its effective asset?

Success at the first says little about the second. A child layout can render its border, background and headings without receiving the asset reference its inner pane needs.

Write down the expected inputs before editing anything:

• The selected asset's unique identifier.
• The content item attached to that asset.
• The content item's assigned type.
• The inner pane's asset reference and type filter.
• Any other selection conditions or runtime access restrictions.

Treat names such as Overview as example configuration values, not universal built-in types. Follow your platform's documented matching rules. Selecting an existing type from a list reduces mistakes with spelling, spaces and capitalization.

Check the content selection without nesting

Use a scratch layout or a copy of the affected view. Keep the diagnostic work separate from controls that can operate equipment.

1. Choose one known asset. Record its identifier and the exact content item you expect to appear.
2. Open that content directly using a supported method. If it cannot load under the runtime account, investigate the content, dependencies and access permissions first.
3. Create a single-pane layout. Remove child layouts, view-switching scripts and unrelated filters from this test.
4. Configure the pane's automatic content selection. Where the platform calls this AutoFill, select the current asset and the intended content type using its documented settings.
5. Navigate to the known asset in runtime. Open the scratch layout through the same supported navigation mechanism used by the application.
6. Inspect the result and available diagnostics. Record whether the selection found no content, selected the wrong item, or selected an item that failed to render.

If the direct content opens but automatic selection does not, focus on the binding inputs. Confirm that the content belongs to the selected asset rather than a similarly named parent or child asset.

If the single-pane layout works, preserve it as a reference. That establishes a working asset-and-type combination in that test context. It does not yet establish that a nested pane receives the same inputs.

Check the asset context inside the child layout

Add a temporary diagnostic label inside the child layout. Bind it to the current asset identifier using a documented layout-context reference. Show the asset name as well if it helps, but use the identifier to distinguish assets with similar names.

Then navigate through the parent layout at runtime and compare the label with the selected asset.

• An empty identifier suggests that the label has no usable asset context, though a label-binding error is also possible.
• A different identifier suggests a fixed, inherited or stale context that does not match navigation.
• The expected identifier shows that the label's binding can resolve the intended asset.

The last result is useful, but it is not conclusive for the pane. A label and a content pane can use different context scopes. Inspect the pane's own effective asset reference through its documented properties or runtime diagnostics where available.

Compare the nested pane with the working scratch pane. Check inherited values, explicit asset overrides, additional filters and refresh settings. Change one setting at a time so the result identifies which difference mattered.

Choose a supported binding design

Do not assume that moving automatic selection outward always fixes the problem. Choose the simplest structure supported by the platform's documentation.

Moving selection to the parent can remove one context handoff. However, selecting a layout as content does not automatically resolve every binding inside it. Its graphics still need valid references or supported parameters.

If the child accepts an explicit asset input, bind that input through the documented mechanism. Avoid undocumented object properties or scripts that depend on internal layout details.

For a display that also contains operating controls, keep monitoring and control requirements distinct. The difference between a factory status display and an operator HMI matters when deciding what must remain available during a view-loading fault.

Add view switching only after static selection works

For a two-view interface, first prove each view independently on the same asset. Example type values might be View2D and View3D, provided your project defines and supports them.

Before adding a button or tab action, check whether the runtime supports changing the pane's type filter, replacing its content reference, or navigating to another parameterized layout. These are different mechanisms. Use the documented one rather than assuming that a property writable in the editor is writable at runtime.

Keep the asset identifier unchanged while selecting each view manually. Confirm the intended layout and graphic appear before connecting the selection to a script.

For asynchronous loading, use the platform's supported request or navigation lifecycle so a late result for the previous asset cannot replace the current view. If no such behavior is documented, simplify the navigation design rather than guessing how to cancel or order requests.

Where one view per asset is expected, make the mapping unambiguous. If multiple content items can share a type, establish the documented selection rule instead of relying on whichever item happens to appear first.

Make missing content visible

Provide distinct states for loading, missing content and loading errors where the runtime exposes those conditions:

• Loading: the selected view is still being resolved or opened.
• No view configured: the asset has no content matching the selected view type.
• Unable to load view: content was selected, but opening or rendering it failed.

Base the message on an actual result or documented status property. Do not infer missing content merely because the pane looks blank. A valid graphic could have an empty background or take time to load.

Keep the selected asset and view name visible outside the dynamic pane. Clear the previous graphic or visibly mark it as stale when navigation changes. An old graphic without a warning can be more misleading than an empty pane.

A view-loading message is not a replacement for alarms or safety functions. Do not hide a required operating indication behind optional layout selection.

Check the complete navigation path

Finish with a repeatable runtime check:

1. Open an asset with both configured views and confirm the asset identifier.
2. Select each view and verify the expected content, not just the layout frame.
3. Navigate to another asset and repeat both selections.
4. Open an asset missing one view and confirm the missing-content message.
5. In a non-production copy, use a known loading-error case and confirm it is distinguished from missing content.
6. Switch assets and views quickly enough to expose stale results, while keeping the test separate from equipment operation.
7. Close and reopen the runtime view through its normal navigation path.

Record the asset identifier, selected type, resolved content identifier and visible result for each case. Remove temporary diagnostic labels only after the intended bindings work. Retain enough supported diagnostics to distinguish a selection problem from a rendering problem when the layout is changed later.

Questions