Module - Ultra Charts
Module - Ultra Charts
Breadcrumbs

Troubleshooting & Support


Use this section to resolve common issues, understand limitations, and find testing strategies.

Troubleshooting Approach

Start with the standard Ignition checks: module state, Gateway and Designer logs, Perspective project access, component configuration, and browser rendering. Reproduce the issue with a small static data set before investigating live bindings or complex chart settings.

Common Problems

The Module Does Not Start

Symptoms

The module is not shown as running, or the Ultra Charts palette category is unavailable.

Possible Causes

  • The installed artifact does not match the documented platform requirement.

  • Perspective is not installed or available.

  • The module installation did not complete successfully.

Recommended Checks

  • Confirm the Gateway and module version against Requirements & Compatibility.

  • Review standard Gateway module status and logs.

  • Confirm that Perspective is installed.

Resolution

Correct the compatibility or installation issue, then reload the affected Designer session.

The Ultra Charts Palette Category Is Missing

Symptoms

The Gateway module appears available, but the Designer palette does not contain Ultra Charts.

Possible Causes

  • The Designer was opened before the module was installed or updated.

  • Perspective is not available in the Designer session.

  • Component registration failed during startup.

Recommended Checks

  • Close and reopen the Designer.

  • Confirm that a Perspective view is open.

  • Review Gateway and Designer logs for module startup or registration errors.

Resolution

Address the reported platform or startup issue, then reopen the Designer and check the palette again.

A Chart Has No Visible Data or Shows an Error

Symptoms

The chart is blank or renders an error instead of the expected visual.

Possible Causes

  • The binding does not return the expected data shape.

  • Configured mark fields do not match the supplied data.

  • The component has no usable display size.

  • A chart option or custom visualization is invalid.

Recommended Checks

  • Replace the binding temporarily with a small static data set.

  • Confirm field names and value types used by the chart configuration.

  • Confirm that the component has usable width and height in the view.

  • Review browser developer tools for rendering errors.

Resolution

Correct the data, binding, or chart configuration, then preview the view again.

A Plot Interaction Does Not Produce the Expected Result

Symptoms

onSelect or onBrush does not fire, or the event result is not useful for the configured chart.

Possible Causes

  • The event handler was not configured in Perspective.

  • The chart configuration does not provide a compatible selection or brush interaction.

  • The data transformation or chart type does not map cleanly back to the original data rows.

Recommended Checks

  • Confirm the event name and handler in the Perspective event editor.

  • Test with a simple chart and small static data set.

  • Review any transformations, facets, or non-continuous scales used by the chart.

Resolution

Adjust the chart and interaction configuration, then validate the event in the intended Perspective session.

A Sankey Chart Does Not Render as Expected

Symptoms

The chart is blank, incomplete, or does not respond to clicks.

Possible Causes

  • Nodes are missing unique names.

  • Links reference nodes that are not present.

  • Link values are not numeric.

  • Node or link click behavior is not enabled.

Recommended Checks

  • Validate node names and link references.

  • Confirm that each link has a numeric flow value.

  • Enable the relevant click option before testing onNodeClick or onLinkClick.

Resolution

Correct the input data or interaction setting and retest with a minimal node-and-link example.

Expert-mode Does Not Render

Symptoms

The custom chart is blank or displays a browser-rendering error.

Possible Causes

  • The chart code is missing, invalid, or does not produce a browser visual.

  • The code expects data that the binding does not provide.

  • The code depends on unavailable browser context or external state.

Recommended Checks

  • Test the code with a small static data value.

  • Review browser developer tools for the reported error.

  • Confirm that the code and data are controlled by a trusted project developer.

Resolution

Correct the project-authored code or data binding, then retest before deployment.

A Chart Displays a License Notice

Symptoms

The component displays a notice indicating that it is not licensed.

Recommended Checks

  • Confirm that the module is running normally in the Gateway.

  • Reload the Perspective session and review Gateway and browser logs.

  • Verify the deployment against the applicable product and Ignition licensing terms.

Resolution

Do not attempt to bypass licensing or access controls. Escalate persistent license-state issues through the approved product-support channel with sanitized diagnostic information.

Last updated: