Modify the parts of your converted code in LabVIEW NXG where behavior differs between LabVIEW and LabVIEW NXG, to replicate the behavior of your original LabVIEW source code.
The following tables describe the possible severity levels and category tags of conversion messages.
|ManualFix||The Code Conversion Utility did not convert the associated item to a runnable state. You must update the associated item to restore dataflow in the converted code. This is the highest severity level for a message.|
|ReviewRequired||The associated item changed in some way, and the runtime behavior of the item may differ from the original source code. The change may or may not affect the behavior of the code, so you should review this change in the editor to determine whether you need to update the associated item.|
|Info||The Code Conversion Utility changed the associated item in a way that does not affect the behavior of the code. You do not need to take any action for info messages.|
|Error||The Code Conversion Utility encountered an unexpected error. Contact NI Support for conversion messages with the category tag Error.|
|NotConverted||The Code Conversion Utility could not access a missing file, a file in vi.lib, a password protected file, or an unlicensed file.|
|SourceFile||Address the associated message in the original source code.|
|Placeholder||The Code Conversion Utility replaced a section of the original source code with a placeholder node. The Code Conversion Utility uses placeholder nodes to preserve dataflow for unsupported features or missing subVI references.|
|Panel||Something changed on the panel. Most converted code contains many minor changes to the panel, especially for VIs that include complex panels.|