LabVIEW NXG 3.0 Web Module Known Issues

Overview

This document contains known issues for the LabVIEW NXG 3.0 Web Module. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered. The LabVIEW 2018 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.

Fields

Each Issue appears as a row in the table and includes these fields:

  • Issue ID
  • Issue Title
  • Problem Description
  • Workaround
  • Reported Version - the earliest version of the LabVIEW NXG Web Module in which the issue was reported
  • Resolved Version - version the issue was resolved or was no longer applicable
  • Date Added - the date the issue was added to the document (not reported date)



Document Organization

Please refer to Developer Zone Article "LabVIEW Known Issues Categories Defined" for an explanation of the categories and what types of issues are in each category.

Contacting NI

You can contact us by phone, email, or the discussion forums. Visit the NI Website to contact us. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in this document.

Known Issues by Category

The following items are known issues in LabVIEW NXG 3.0 Web Module sorted by Category.

Controls and Indicators
666046Radio Button Group does not resize when additional Radio Buttons are added
666287Warning when copying a Graph from a VI's Diagram to a Web VI's Diagram
666581Dragging multiple arrays into a tab control can cause visual issues
667678Error clusters always display information in the source string even if no error occurred
External Code
673324Adding items to the FrontPanelCanvas tags in the HTML panel always places the new items at the top of the section
Functions, VIs, and Express VIs
664268VI snippets do not create controls on the Panel when placed in a Web VI
666182When attempting to create a sub VI from code on a Web VI, you can only create a sub Web VI
669020String to Number functions may return incorrect values when converting to I64 or U64 data types in Web VIs
671454Providing a username and password when a cross-origin request results in a 401 has varying behavior between browsers. In the LabVIEW NXG editor this will result in a timeout.
659068Creating a Web VI in a project results in a broken run arrow on the Web VI
713702If the Add/Multiply node is coercing the value, JavaScript errors are thrown in the WebVI
LabVIEW Project
667774The Output tab does not allow horizontal scrolling



IDKnown Issue
Controls and Indicators
666046

Return
Radio Button Group does not resize when additional Radio Buttons are added

Workaround: N/A

Reported Version: 2.0  Resolved Version: N/A  Added: 01/23/2018
666287

Return
Warning when copying a Graph from a VI's Diagram to a Web VI's Diagram
When you copy a VI's Diagram contents and paste them on a Web VI's Diagram, a warning will appear if one of the items is a Graph indicator.

Workaround: Delete the graph terminal and create a new Graph in the Web VI

Reported Version: 2.0  Resolved Version: N/A  Added: 01/23/2018
666581

Return
Dragging multiple arrays into a tab control can cause visual issues

Workaround: Save the Web VI and reopen it, or drag a single element into the tab at a time

Reported Version: 2.0  Resolved Version: N/A  Added: 01/23/2018
667678

Return
Error clusters always display information in the source string even if no error occurred

Workaround: N/A

Reported Version: 1.0  Resolved Version: N/A  Added: 01/23/2018
External Code
673324

Return
Adding items to the FrontPanelCanvas tags in the HTML panel always places the new items at the top of the section
Because the items that are added are always at the top of the section, the content that is added will always appear behind the content that LabVIEW NXG creates

Workaround: Set the z-index property for the item that is being added

Reported Version: 2.0  Resolved Version: N/A  Added: 01/23/2018
Functions, VIs, and Express VIs
664268

Return
VI snippets do not create controls on the Panel when placed in a Web VI

Workaround: N/A

Reported Version: 2.0  Resolved Version: N/A  Added: 01/23/2018
666182

Return
When attempting to create a sub VI from code on a Web VI, you can only create a sub Web VI

Workaround: N/A

Reported Version: 2.0  Resolved Version: N/A  Added: 01/23/2018
669020

Return
String to Number functions may return incorrect values when converting to I64 or U64 data types in Web VIs
When converting from strings to 64-bit numbers, the String to Number functions (Decimal String to Number, Hex String to Number, etc.) can return unexpected results

Workaround: N/A

Reported Version: 2.0  Resolved Version: N/A  Added: 01/23/2018
671454

Return
Providing a username and password when a cross-origin request results in a 401 has varying behavior between browsers. In the LabVIEW NXG editor this will result in a timeout.

Workaround: N/A

Reported Version: 2.0  Resolved Version: N/A  Added: 01/23/2018
659068

Return
Creating a Web VI in a project results in a broken run arrow on the Web VI
N/A

Workaround: When a Web VI is created, it is targeted to the "This Computer" target. Web VIs must exist in a Web Application (application targeted to a Web Server target) in order to run. Create a Web Server target in SystemDesigner, then create an application on the target and add your Web VI to the application.

Reported Version: 2.0  Resolved Version: N/A  Added: 03/21/2018
713702

Return
If the Add/Multiply node is coercing the value, JavaScript errors are thrown in the WebVI
If the Add/Multiply node is set to coerce the output value, JavaScript throws errors when the WebVI is run.

Workaround: Convert the values manually in the code.

Reported Version: 3.1  Resolved Version: N/A  Added: 10/26/2018
LabVIEW Project
667774

Return
The Output tab does not allow horizontal scrolling

Workaround: Copy the text from the Output tab into another location and read the message there

Reported Version: 1.0  Resolved Version: N/A  Added: 01/23/2018

Document last updated on 10/26/2018

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).