Archived: Measurement Studio 2010 and 2010 SP1 Known Issues by Date

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Überblick

This document contains the <product> <version> known issues that were discovered before and since the release of <product> <version>. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.

 

Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.

Overview

This document contains the Measurement Studio 2010 known issues that were discovered before and since the release of Measurement Studio 2010. 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.

Each known issue includes these fields:

  • Issue ID
  • Legacy ID - The issue's legacy ID from NI's deprecated bug reporting database (if applicable)
  • Issue Title
  • Problem Description
  • Workaround
  • Reported Version - the earliest version of Measurement Studio the issue was reported in
  • Resolved Version - version the issue was resolved or was no longer applicable
  • Date Added - the date the issue was added to the document (not the reported date)

Document Organization

The Known Issues Document is divided into two separate tables appearing in two separate Developer Zone documents. The known issues in this document are organized by the date they were added to this document. To view the issues organized by category, visit the document linked below:

Known Issues by Category

Contacting NI

You can contact us through any of the normal support channels including 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 the document to the NI representative.

Known Issues by Date

The following items are known issues in Measurement Studio 2010 sorted by Date.

111651 The error, "Attempting to deserialize an empty stream", sometimes occurs when you attempt to build a Web Site project using Measurement Studio controls.
120249 If you copy and paste dynamically filtered help content into a text editor, such as Microsoft Word, you may see content that applies to components not installed on your machine.
122353 Mouse cursor changes to the default mouse cursor after zooming.
133220 4B89AJ00 Network variable performance decreases when machines hosting the reader, writer, and variables are mixed between Logos and LogosXT.
133256 4DDCC0IO Creating network variables causes a small memory leak
133322 In some circumstances, you receive error, HRESULT E_FAIL, when using the DAQ Application Project Wizard.
133332 When the Windows Forms Designer and a source code window are both open, and the Windows Forms Designer is active, the Parameter Assistant does not restrict code from being inserted into the source file.
133380 In some circumstances, the network variable class library deadlocks if you are stepping through code in a network variable class library event handler.
133384 In some instances, running your Visual C++/CLI project results in unlicensed exceptions.
133396 Under some circumstances, plots with data that extend outside the plot area are clipped incorrectly.
133413 The Windows Forms Designer presents an error page stating that parts cannot be found.
133439 Links to hardware class library documentation may be broken if you do not have the latest hardware drivers installed.
31138 435E06I0 Calling DoEvents in a NumericEdit control callback may cause an exception.
31271 40A7S0HW Editing an axis interactively and then calling PlotYAppend from the AutoRefresh callback with a fixed axis erases the previous committed axis value.
96497 Calling ShowDialog on a Windows Form that contains a property editor control might cause an InvalidCastException.
98865 3ZNCBRAF If you create a managed Visual C++ project using the Windows Application template, put a Measurement Studio .NET control on the form, and add a setup project to the solution using the primary output of the C++ project, you will receive a missing file error when you build.
115770 Measurement Studio UI controls that are part of a custom Web control do not display during design time.
33786 Undo does not work for some Measurement Studio .NET properties when edited from the Microsoft Visual Studio Designer.
168274 Reading and writing data within the same loop using TDMS results in a significant performance decrease.
181843 Dropping a Measurement Studio .NET control into a Visual Studio Web application at design time may result in an error.
181874 The Datasocket "Select URL" dialog may crash Visual Studio when using Windows Vista.
182120 Network Variable does not support variables with the Timestamp data type.
191580 Uninstalling National Instruments products may also remove installed .NET applications that use National Instruments libraries.
191880 Matrix operations that utilize the Intel MKL on Windows have slight numerical difference between Measurement Studio 2009 and prior Measurement Studio versions.
199947 Significant decrease in performance occurs when using NI-488.2 for Microsoft Windows and LabVIEW Real-Time
176144 32-bit analysis and 64-bit analysis library results can have slight numerical differences
222719 Custom division labels may be clipped on the far right side of the x-axis of the intensity graph.
295320 The function GaussHG returns NaN for X values less than 0.
208239 ClipDataPoints returns an extra point when used on a WavefromPlot.
208242 The ClipDataPoints method does not work for ScatterPlot objects.
211806 Intellisense does not display help for methods containing a 2D array as a parameter for Visual C# projects in Visual Studio 2005.
216981 Modifying a collection property of a .NET control from the Visual Studio Designer might not always work.
217352 Updating the InteractionModeDefault of any .NET graph while the mouse is over the graph will not update the mouse cursor.
220060 The 64-bit Logos merge module does not contain the commands necessary to install necessary Logos services.
221889 If a Measurement Studio assistant runs while Measurement and Automation Explorer (MAX) is open, creating future Visual Studio projects will fail, but only if this is the first time you are creating a Visual Studio project.
222524 The y-axis will accomodate the text length of a custom division label even if the custom division is not visible.
235390 Boolean controls do not correctly handle the Escape key.
235391 Measurement Studio .NET boolean controls do not correctly handle loss of application focus.
239529 Autoformatting a .NET waveform, scatter, complex, or intensity graph at design time removes captions from existing annotations.
240646 The background of Measurement Studio .NET controls does not remain transparent when the controls are disabled.
244273 A project using Measurement Studio mixed mode assemblies built against .NET Frameworks prior to .NET Framework 4 cannot run against .NET Framework 4.
251034 Zoom animation is drawn even when a .NET graph has not been added to a Windows Form.
251984 Waveform timing information is lost if a network variable with a waveform type is bound to a waveform graph.
254498 Waveform, scatter, complex, and intensity.NET graph annotations do not appear in the correct position if moved from one graph to another.
254812 The following device drivers do not include Visual Studio 2010 support: MAX Configuration Utility, NI-IMAQ, NI-IMAQdx, and NI-SCOPE.
257280 Generating an NI-DAQmx component and an Instrument Driver component in VB.NET results in a project that will not build.
276792 The Update Project References dialog box shows an evaluation warning.
288758 The Measurement Studio tank control displays a red bar when oriented horizontally.
198036 Vertical captions on Measurement Studio controls do not display correctly in some languages, such as Korean, Japanese, and Chinese.
257272 EngineeringFormatInfo.Parse fails when used with non-English numeric separators.
276432 The debugger display strings in Visual Studio for the Measurement Studio intensity graph are not consistent with other Measurement Studio graphs.
276435 If you call the Draw method on a Measurement Studio annotation and the Visible property of the annotation is set to false, the annotation does not draw.
278468 The DAQmxWithUI examples do not work unless you have purchased Measurement Studio Enterprise Edition.
285295 You cannot evaluate Measurement Studio on Italian versions of Windows.
286749 If a Measurement Studio control is on a Microsoft tab control, saving the control to an image results in a poor-quality image.
286890 The Evaluate Products button on the Measurement Studio Activation dialog box is not localized for non-English operating systems.
290072 Zooming on a Measurement Studio graph does not work correctly when the axes are inverted.
290486 Using a logarithmic x-axis scale on Measurement Studio graphs can cause a hang for some data sets.
292544 Deployed Measurement Studio network variable client programs cannot use LogosXT.
297181 Building a Measurement Studio ASP.NET Web Forms project fails on computers with United States Federal Information Processing Standard (FIPS) enabled.
297766 The Instrument Driver Wizard crashes Visual Studio 2010 when trying to generate a wrapper for niHSDIO.fp.
300030 Excessive licensing dialog boxes display while evaluating Measurement Studio on a United States Federal Information Processing Standard (FIPS) enabled computer.
301621 The Measurement Studio Help is not uninstalled when Measurement Studio has been uninstalled.
302132 Cloning a ScatterPlot object does not clone the ProcessSpecialValues property.
306771 In the Measurement Studio Help for Visual Studio 2010, links from Measurement Studio conceptual help topics to methods that have parameters and are not overloaded do not work.
309646 When drawing very thick plot lines on a Measurement Studio .NET graph, the line can draw incorrectly.
310916 When using a Debug Deployment license, a dialog box states that there is "No License Available" when launching Visual Studio for the first time.
291290 Distributing Measurement Studio applications to computers with User Account Control (UAC) enabled can result in an incomplete installation.
291489 Running the HelpConfigurationUtility from a directory other than the one the utility is in causes the Help button to break.
291673 Adding a Measurement Studio control to a Web User Control in an ASP.NET Web application project might result in an error.
292392 Calling Filter.Reset can change the characteristics of the filter.
292897 Upgrading from Measurement Studio 2009 to Measurement Studio 2010 can result in failing distribution builds from other National Instruments software.
294382 64-bit TDMS applications might crash when reading properties.
295481 When targeting a previous .NET Framework version in Visual Studio 2008 or Visual Studio 2010, the Measurement Studio Update Project References wizard attempts to update your project references to the latest .NET Framework version.
297106 Uninstalling an application that uses network variable leaves behind the network variable assembly in the Global Assembly Cache (GAC).
298877 Adding Measurement Studio .NET 3.5 assemblies to an ASP.NET Web site that targets .NET 4.0 results in incorrect dependencies added to the project.
307898 The Measurement Studio License Status dialog box sometimes displays a button named "Launch Product" instead of "Evaluate Products"
284835 You cannot de-select the Web Forms User Interface Control Library from the Add/Remove Class Libraries Wizard.
296833 The Parameter Assistant throws an exception and does not respond when browsing Source URL for NI DataSocket.
314617 Measurement Studio ActiveX controls cause all controls to not anchor to right side of form.
317267 If the Annotations do not have explicitly assigned axes, Annotations do not appear until the Windows Forms scatter or waveform graph is redrawn.
317292 The range fill for the Windows Forms Slide control shrinks when slider moves at run-time.
322666 Istantiating a ComplexDouble for the first time takes a longer than expected.
328010 Installing Measurement Studio 2010 SP1 for Visual Studio 2010 Express without integration support results in being unable to activate.
332295 The Windows Forms ScatterGraph displays a red "x" when out of memory, but does not throw an exception.
335548 Using the ZoomXY method on a Windows Forms ScatterGraph throws an exception when the y-axis is using a logarithmic scale type.
337384 Windows Forms Plot3DMesh causes an exception when run multiple times with a large number of points.
338809 Windows Forms Graph axis label spacing is determined based the end labels, even if the end labels are not visible.
316607 The WaveformGraph Plot with ProcessSpecialValues set to true hangs when double.PositiveInfinity is plotted or crashes when double.NegativeInfinity is plotted.
319689 Modifications to the Range values in a Windows Forms graph using the dialog editor are not committed if only the Min value is changed.
320362 The Measurement Studio .NET XCOPY Deployment Files help topic for Visual Studio 2010 lists msvcm100.dll as a dependency.
338874 If you set the WebForms InteractionMouseCursor property through the designer, the page does not save when using certain controls.
344059 Custom install locations are ignored when National Instruments Merge Modules target is set to the Module Retargetable Folder.
349762 The Windows Forms NumericEdit control does not initialize to a NaN value.
355871 The ChebyshevLowpassFilter() documentation incorrectly lists stopbandRipple as a parameter instead of passbandRipple.
360932 The displayed scales for the Slide, Thermometer, and Tank WindowsForms controls do not accurately map to a value.
361842 Icons for DataSocket URLs do not display with the DataSocket.SelectUrl popup.
370422 The HarmonicAnalyzer method in the Analysis Spectral Measurement library throws an AccessViolationException regardless of the input.
373901 Appending data to a cloned WaveformPlot object causes a NullReferenceException to be thrown.
384987 The PropertyChanged event does not occur when the Plot property of a XYCursor changes.
338802 Calling the ClearData method on the Windows Forms DigitalWaveformGraph control a second time on an empty graph causes the horizontal scrollbar to disappear.
373911 Visual Studio crashes when the Instrument Driver Wizard attempts to load a function panel file (.fp) when an associated .sub file is encoded as unicode.



ID Known Issue
111651

Return
The error, "Attempting to deserialize an empty stream", sometimes occurs when you attempt to build a Web Site project using Measurement Studio controls.
On Microsoft Windows Vista x64, when using Visual Studio 2008 without Service Pack 1 installed, the error "Attempting to deserialize an empty stream" occurs when you attempt to build a Web Site project using Measurement Studio controls.

Workaround: Upgrade Visual Studio 2008 to Service Pack 1.

Reported Version: 8.5    Resolved Version: N/A    Added: 11/17/2008
120249

Return
If you copy and paste dynamically filtered help content into a text editor, such as Microsoft Word, you may see content that applies to components not installed on your machine.
At page load time, Measurement Studio dynamically filters documentation based on the components or package you have installed. If you copy and paste dynamically filtered help content into a text editor, such as Microsoft Word, you may see content that applies to components not installed on your machine.

Workaround: N/A

Reported Version: 8.1.2    Resolved Version: N/A    Added: 11/17/2008
122353

Return
Mouse cursor changes to the default mouse cursor after zooming.
After zooming in on a waveform graph in a Measurement Studio .NET WebForms application, the mouse cursor changes to the default mouse cursor until you move the mouse.

Workaround: N/A

Reported Version: 8.0.1    Resolved Version: N/A    Added: 11/17/2008
133220
4B89AJ00


Return
Network variable performance decreases when machines hosting the reader, writer, and variables are mixed between Logos and LogosXT.
Logos is the National Instruments proprietary protocol for inter-process communication that is used by NI-Publish Subscribe Protocol (psp:). Performance is especially degraded when the writer and network variable host use LogosXT and the reader that attempts to read the network variable uses Logos. This issue occurs for all reader classes.

Workaround: For optimum performance, National Instruments recommends that all machines accessing network variables, including the machine that hosts the variable, should use LogosXT. If using LogosXT on all machines is not possible, you should disable LogosXT. You disable LogosXT by adding a DWORD value named DisablePSPXT to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\LogosXT and setting its value to 1. If you must use a mix of Logos versions, you can reduce the performance loss by using Variable Manager. Use Variable Manager to configure a sufficiently large server-side buffer for the network variable.

Reported Version: 8.1.2    Resolved Version: N/A    Added: 11/17/2008
133256
4DDCC0IO


Return
Creating network variables causes a small memory leak
Creating a network variable using the ServerVariable.Create or ServerVariableInfo.Create methods results in a memory leak of approximately 50 bytes per variable that is created.

Workaround: Consider using implicitly created network variables if you are creating and deleting numerous variables over a long period of time.

Reported Version: 8.5    Resolved Version: N/A    Added: 11/17/2008
133322

Return
In some circumstances, you receive error, HRESULT E_FAIL, when using the DAQ Application Project Wizard.
When you use the DAQ Application Project Wizard within Visual Studio, Visual Studio occasionally gets into a state where it reports the following error: Error HRESULT E_FAIL has returned from a call to a COM component.

Workaround: Restart Visual Studio to fix this issue.

Reported Version: 8.0.1    Resolved Version: N/A    Added: 11/17/2008
133332

Return
When the Windows Forms Designer and a source code window are both open, and the Windows Forms Designer is active, the Parameter Assistant does not restrict code from being inserted into the source file.
Instead, code is inserted into the source file at the last cursor location, which might have been changed by the Windows Forms Designer.

Workaround: N/A

Reported Version: 7.0    Resolved Version: N/A    Added: 11/17/2008
133380

Return
In some circumstances, the network variable class library deadlocks if you are stepping through code in a network variable class library event handler.
The network variable class library deadlocks if you are stepping through code in a network variable class library event handler and you are watching any of the following properties in the Debugger Watch Window:
  •  ConnectionStatus,
  •  NetworkVariableBufferedSubscriber.ItemCapacity,
  • NetworkVariableBufferedSubscriber.ItemCount,
  •  NetworkVariableBufferedWriter.ItemCapacity, or
  • NetworkVariableBufferedWriter.ItemCount.
When the Debugger evaluates properties in the Watch Window, it freezes all other threads except the currently executing thread. When the network variable thread is frozen, the network variable class library deadlocks.

Workaround: To work around this issue, do not add the properties listed above to the Watch Window when stepping through network variable event handler code.

Reported Version: 8.1    Resolved Version: N/A    Added: 11/17/2008
133384

Return
In some instances, running your Visual C++/CLI project results in unlicensed exceptions.
In Visual C++/CLI projects, when you drop a Measurement Studio control on a form, Visual Studio references the Measurement Studio assemblies from the GAC. If you select Measurement Studio»Refresh Project License File, the contents of the .licx file are cleared. Without the proper contents in the .licx file, running your project results in unlicensed exceptions.

Workaround: To refresh the .licx file, select Measurement Studio»View .NET Class Library Wizard. In the Measurement Studio .NET Class Library Wizard dialog box, deselect the Measurement Studio libraries and close the dialog box. Run the Measurement Studio .NET Class Library Wizard again and select the Measurement Studio libraries.

Reported Version: 8.0    Resolved Version: N/A    Added: 11/17/2008
133396

Return
Under some circumstances, plots with data that extend outside the plot area are clipped incorrectly.
As a result, part of the plot is not drawn. Microsoft has confirmed that this is a problem with clipping in the .NET Framework.

Workaround: N/A

Reported Version: 7.0    Resolved Version: N/A    Added: 11/17/2008
133413

Return
The Windows Forms Designer presents an error page stating that parts cannot be found.
If your project references NationalInstruments.UI.WindowsForms, but does not reference the assemblies it depends on, there are circumstances in which the Windows Forms Designer presents an error page stating that parts cannot be found. This occurs when the Windows Forms Designer re-parses its generated code and is unable to resolve references to types that are in the assemblies that NationalInstruments.UI.WindowsForms depends on.

Workaround: To fix this problem, add project references to NationalInstruments.UI and NationalInstruments.Common. Measurement Studio does this for you automatically, so you see this issue only if you disable Measurement Studio integration features in Visual Studio.

Reported Version: 7.0    Resolved Version: N/A    Added: 11/17/2008
133439

Return
Links to hardware class library documentation may be broken if you do not have the latest hardware drivers installed.

Workaround: Use the Contents, Index, or Search tabs instead to find the topic.

Reported Version: 8.0    Resolved Version: N/A    Added: 11/17/2008
31138
435E06I0


Return
Calling DoEvents in a NumericEdit control callback may cause an exception.
When using the NumericEdit control, if a call is made to DoEvents inside either the ValueChange event or the AfterValueChangeEvent and the button is pressed rapidly, the control throws an exception. This error can also occur if the event handlers take a while to return. Microsoft has confirmed that this is a problem with the NumericUpDown control in the .NET Framework.

Workaround: N/A

Reported Version: 8.0.1    Resolved Version: 2010 SP1    Added: 11/17/2008
31271
40A7S0HW


Return
Editing an axis interactively and then calling PlotYAppend from the AutoRefresh callback with a fixed axis erases the previous committed axis value.

Workaround: Put the control inside an UpdatePanel and plot data using the timer tick event

Reported Version: 8.1    Resolved Version: N/A    Added: 11/17/2008
96497

Return
Calling ShowDialog on a Windows Form that contains a property editor control might cause an InvalidCastException.
Calling ShowDialog on a Windows Form that contains a property editor control linked to a Measurement Studio .NET control from a non-UI thread causes an InvalidCastException.

Workaround: Use SetApartmentState() to set the ApartmentState of the thread created to ApartmentState.STA.

Reported Version: 8.1.2    Resolved Version: N/A    Added: 11/17/2008
98865
3ZNCBRAF


Return
If you create a managed Visual C++ project using the Windows Application template, put a Measurement Studio .NET control on the form, and add a setup project to the solution using the primary output of the C++ project, you will receive a missing file error when you build.
This is only an issue for Visual Studio 2005.

Workaround: To work around this issue, do not use the primary output option for the setup project. Instead manually add the .exe and the required .msm files to the project.

Reported Version: 8.0.1    Resolved Version: N/A    Added: 11/17/2008
115770

Return
Measurement Studio UI controls that are part of a custom Web control do not display during design time.
This issue has been fixed with the release of Visual Studio 2008 SP1.

Workaround: Upgrade to Visual Studio 2008 SP1. The controls will display correctly at run time even without SP1.

Reported Version: 8.5    Resolved Version: N/A    Added: 01/05/2009
33786

Return
Undo does not work for some Measurement Studio .NET properties when edited from the Microsoft Visual Studio Designer.
Microsoft has confirmed that this is a bug in the Designer and will possibly fix the issue in a future update or version.

Workaround: N/A

Reported Version: 8.0.1    Resolved Version: N/A    Added: 01/30/2009
168274

Return
Reading and writing data within the same loop using TDMS results in a significant performance decrease.

Workaround: Read and write data in separate loops.

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 12/01/2009
181843

Return
Dropping a Measurement Studio .NET control into a Visual Studio Web application at design time may result in an error.
Dropping a .NET control without adding a reference to NationalIntruments.UI results in an error. Note that the Web.Config file and the license files are updated, but the references in the project file are not.

Workaround: Manually add the reference by selecting the Measurement Studio»Add/Remove .NET Class Libraries menu item in Visual Studio.

Reported Version: 8.5    Resolved Version: N/A    Added: 12/01/2009
181874

Return
The Datasocket "Select URL" dialog may crash Visual Studio when using Windows Vista.
The dialog that appears when you click the "Select URL" option for the Datasocket control may crash Visual Studio.

Workaround: N/A

Reported Version: 8.5    Resolved Version: 2012    Added: 12/01/2009
182120

Return
Network Variable does not support variables with the Timestamp data type.
If you try to browse to a process that contains a variable with this data type, calls to GetSubItems() fail. As a result, you cannot browse for items in that process.

Workaround: N/A

Reported Version: 8.1.2    Resolved Version: N/A    Added: 12/01/2009
191580

Return
Uninstalling National Instruments products may also remove installed .NET applications that use National Instruments libraries.

Workaround: N/A

Reported Version: 8.5    Resolved Version: N/A    Added: 12/01/2009
191880

Return
Matrix operations that utilize the Intel MKL on Windows have slight numerical difference between Measurement Studio 2009 and prior Measurement Studio versions.
Measurement Studio 2009 upgrades to use latest version of the Intel MKL library to accelerate linear algebra operations under the Windows operating system. Some functions in latest Intel MKL library return minor differences in the results than previous version of MKL due to different optimizations. This also results in slight numerical difference between Measurement Studio 2009 and previous versions of Measurement Studio. This affects Linear Alegbra functions and some Mathematics functions in LabWindows/CVI.

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 12/01/2009
199947

Return
Significant decrease in performance occurs when using NI-488.2 for Microsoft Windows and LabVIEW Real-Time
You might experience significant loss of GPIB performance after installing or updating NI software on systems using PCI, PCI Express, PMC, or PXI GPIB interface types or built-in interfaces on PXI and VXI controllers. All other GPIB interfaces are not affected. Refer to KnowledgeBase 54EF93G2 for more information about this issue.

Workaround: Refer to KnowledgeBase 54EF93G2 for more information about this issue.

Reported Version: 8.5    Resolved Version: Unknown    Added: 01/08/2010
176144

Return
32-bit analysis and 64-bit analysis library results can have slight numerical differences
For more information about this issue, please refer to KB 51MA76UB: Why are There Minor Differences in Analysis Function Results Between 32-bit and 64-bit LabVIEW, Measurement Studio, or LabWindows/CVI Applications?

Workaround: N/A

Reported Version: 2009    Resolved Version: Unknown    Added: 04/15/2010
222719

Return
Custom division labels may be clipped on the far right side of the x-axis of the intensity graph.

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 05/26/2010
295320

Return
The function GaussHG returns NaN for X values less than 0.

Workaround: N/A

Reported Version: 2009    Resolved Version: 2012    Added: 11/18/2010
208239

Return
ClipDataPoints returns an extra point when used on a WavefromPlot.
ClipDataPoints returns all the visible points, plus the point that falls just to the right and the point that falls just to the left of the clipping bounds. This enables lines to be drawn into and out of the plot area. However, it also returns one additional point that also lies outside the clipping bounds and is not needed for drawing to the plot area.

Workaround: N/A

Reported Version: 8.5    Resolved Version: 2012    Added: 12/03/2010
208242

Return
The ClipDataPoints method does not work for ScatterPlot objects.

Workaround: N/A

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 12/03/2010
211806

Return
Intellisense does not display help for methods containing a 2D array as a parameter for Visual C# projects in Visual Studio 2005.
Measurement Studio methods taking a 2D array as a parameter do not display help for the parameters in the Intellisense for Visual C# projects in Visual Studio 2005.

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 12/03/2010
216981

Return
Modifying a collection property of a .NET control from the Visual Studio Designer might not always work.
For example if you modify the CustomDivisions collection of a component in the Visual Studio Designer, such as XAxis that is included in a collection, such as Plots, the modifications are not saved.

Workaround: When using the Visual Studio Designer, modify collections only from the component that contains them.

Reported Version: 8.6    Resolved Version: N/A    Added: 12/03/2010
217352

Return
Updating the InteractionModeDefault of any .NET graph while the mouse is over the graph will not update the mouse cursor.
The cursor will not update until the mouse moves off and then back onto the graph.

Workaround: Manually setting the Cursor property updates the cursor, but you must restore the cursor when the mouse leaves the graph for the first time.

Reported Version: 8.6.1    Resolved Version: 2010 SP1    Added: 12/03/2010
220060

Return
The 64-bit Logos merge module does not contain the commands necessary to install necessary Logos services.

Workaround: If you are creating a 64-bit distribution that requires the Logos merge module, you must also include the 32-bit merge module in your distribution.

Reported Version: 2009    Resolved Version: N/A    Added: 12/03/2010
221889

Return
If a Measurement Studio assistant runs while Measurement and Automation Explorer (MAX) is open, creating future Visual Studio projects will fail, but only if this is the first time you are creating a Visual Studio project.

Workaround: Close MAX and restart Visual Studio.

Reported Version: 8.6.1    Resolved Version: 2012    Added: 12/03/2010
222524

Return
The y-axis will accomodate the text length of a custom division label even if the custom division is not visible.
If you create a custom division on the y-axis with a label long enough to cause the y-axis width to grow, the axis does not return to its normal size if the custom division is not visible.

Workaround: N/A

Reported Version: 8.6    Resolved Version: 2010 SP1    Added: 12/03/2010
235390

Return
Boolean controls do not correctly handle the Escape key.
For example, when an LED or Switch has an interaction mode of SwitchWhenReleased, you cannot press Escape to cancel the change.

Workaround: N/A

Reported Version: 8.0.1    Resolved Version: 2010 SP1    Added: 12/03/2010
235391

Return
Measurement Studio .NET boolean controls do not correctly handle loss of application focus.
You can see this behavior if the following steps occur:
  1. You set the interaction mode of the boolean control to SwitchUntilReleased.
  2. Start the application, and another small application you can switch to.
  3. You press and hold the mouse over the boolean control.
  4. You Alt+Tab to another application while still holding down the mouse.
  5. You move the mouse away from the control and release.
If you do these steps, the boolean control is stuck in the true position. Returning the focus to the application does not correct the state of the boolean control.

Workaround: N/A

Reported Version: 8.0.1    Resolved Version: 2010 SP1    Added: 12/03/2010
239529

Return
Autoformatting a .NET waveform, scatter, complex, or intensity graph at design time removes captions from existing annotations.

Workaround: N/A

Reported Version: 8.5    Resolved Version: N/A    Added: 12/03/2010
240646

Return
The background of Measurement Studio .NET controls does not remain transparent when the controls are disabled.
When you disable a Measurement Studio control, even with the background color to transparent, the entire area of the control is grayed out when you run your program.

Workaround: Set the form background color to ButtonHighlight. This is the same color as the background color for the disabled control.

Reported Version: 2009    Resolved Version: N/A    Added: 12/03/2010
244273

Return
A project using Measurement Studio mixed mode assemblies built against .NET Frameworks prior to .NET Framework 4 cannot run against .NET Framework 4.
If you build a Measurement Studio project that references a Measurement Studio mixed mode assembly, such as NationalInstruments.Common.Native in Visual Studio 2005 or 2008, and try to run the project on a machine that has only .NET Framework 4, the project will not run, even when using an app.config file to force it to use .NET Framework 4. The project fails to load the mixed mode assembly.

Workaround: Install the version of the .NET Framework that the application was built against, along with .NET Framework 4.

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 12/03/2010
251034

Return
Zoom animation is drawn even when a .NET graph has not been added to a Windows Form.
The following code reproduces this behavior:
WaveformGraph g = new WaveformGraph();
g.XAxes.Add(new XAxis());
g.YAxes.Add(new YAxis());
g.ZoomXY(0, 0, 0.1f, 0.1f);


Workaround: If the graph does not belong to a Windows Form, turn off zoom animation with the ZoomAnimation property before zooming.

Reported Version: 8.5    Resolved Version: N/A    Added: 12/03/2010
251984

Return
Waveform timing information is lost if a network variable with a waveform type is bound to a waveform graph.
The bound data is plotted based on the indices of the values, and not on the timing information associated with the waveform.

Workaround: Explicitly retrieve the data from the network variable using a NetworkVariableReader or NetworkVariableSubscriber.

Reported Version: 8.6.1    Resolved Version: N/A    Added: 12/03/2010
254498

Return
Waveform, scatter, complex, and intensity.NET graph annotations do not appear in the correct position if moved from one graph to another.

Workaround: Set the positions of the annotation after moving the annotation to the new graph, or you could perform another action on the annotation, like moving the annotation caption..

Reported Version: 2010    Resolved Version: 2010 SP1    Added: 12/03/2010
254812

Return
The following device drivers do not include Visual Studio 2010 support: MAX Configuration Utility, NI-IMAQ, NI-IMAQdx, and NI-SCOPE.

Workaround: N/A

Reported Version: 2010    Resolved Version: 2012    Added: 12/03/2010
257280

Return
Generating an NI-DAQmx component and an Instrument Driver component in VB.NET results in a project that will not build.

Workaround: Manually remove the namespace declaration added to the Instrument Driver component source code.

Reported Version: 8.0    Resolved Version: 2012    Added: 12/03/2010
276792

Return
The Update Project References dialog box shows an evaluation warning.
This evaluation warning displays because the Update Project References dialog box was built with an evaluation version of a third-party software component. This warning does not mean that your copy of Measurement Studio is in the evaluation license state. Despite the evaluation warning, your project references will update successfully.

Workaround: Click OK in the SandGrid for Windows Forms dialog box to continue.

Reported Version: 2010    Resolved Version: 2010 SP1    Added: 12/03/2010
288758

Return
The Measurement Studio tank control displays a red bar when oriented horizontally.
If the Measurement Studio tank control is oriented horizontally and uses the Raised 3D style, a red bar will display at the base of the control.

Workaround: N/A

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 03/17/2011
198036

Return
Vertical captions on Measurement Studio controls do not display correctly in some languages, such as Korean, Japanese, and Chinese.

Workaround: N/A

Reported Version: 8.5    Resolved Version: N/A    Added: 03/22/2011
257272

Return
EngineeringFormatInfo.Parse fails when used with non-English numeric separators.

Workaround: N/A

Reported Version: 2010    Resolved Version: 2010 SP1    Added: 03/22/2011
276432

Return
The debugger display strings in Visual Studio for the Measurement Studio intensity graph are not consistent with other Measurement Studio graphs.
The debugger display string for the intensity graph shows {PlotAreaColor={Color[Black]}} instead of {Plots = 1}, like other Measurement Studio graphs.

Workaround: N/A

Reported Version: 2010    Resolved Version: 2010 SP1    Added: 03/22/2011
276435

Return
If you call the Draw method on a Measurement Studio annotation and the Visible property of the annotation is set to false, the annotation does not draw.
All other Measurement Studio user interface components draw correctly when you call Draw, even if the Visible property is set to false.

Workaround: Ensure the Visible property of the annotation is set to true before drawing the annotation.

Reported Version: 2009    Resolved Version: 2010 SP1    Added: 03/22/2011
278468

Return
The DAQmxWithUI examples do not work unless you have purchased Measurement Studio Enterprise Edition.
These examples reference the Enterprise version of the Measurement Studio Analysis assembly.

Workaround: Remove the reference to NationalInstruments.Analysis.Enterprise and add the reference you are licensed to use. For example, if you have Measurement Studio Professional, add a reference to NationalInstruments.Analysis.Professional.

Reported Version: 2010    Resolved Version: 2012    Added: 03/22/2011
285295

Return
You cannot evaluate Measurement Studio on Italian versions of Windows.
Attempting to run any projects built while evaluating Measurement Studio results in a LicenseException.

Workaround:
  1. In the Control Panel, double-click Regional and Language Options.
  2. In the Regional Options tab, under Standards and Formats, change the format to English, United States. (Inglese (Stati Uniti) in Italian.)
  3. Rebuild all previously built projects.


Reported Version: 2010    Resolved Version: 2010 SP1    Added: 03/22/2011
286749

Return
If a Measurement Studio control is on a Microsoft tab control, saving the control to an image results in a poor-quality image.
If you save the image as a .png file, the image quality is poor. If you save the image as a .jpeg or .bmp file, the image is entirely black.

Workaround: Assign a nontransparent color to the BackgroundColor property of the Measurement Studio control before creating an image of the control.

Reported Version: 2010    Resolved Version: 2010 SP1    Added: 03/22/2011
286890

Return
The Evaluate Products button on the Measurement Studio Activation dialog box is not localized for non-English operating systems.

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 03/22/2011
290072

Return
Zooming on a Measurement Studio graph does not work correctly when the axes are inverted.
When you zoom with an inverted axis, the zoom algorithm ignores the inversion, which results in a zoom to a different region than was selected.

Workaround: N/A

Reported Version: 2010    Resolved Version: 2010 SP1    Added: 03/22/2011
290486

Return
Using a logarithmic x-axis scale on Measurement Studio graphs can cause a hang for some data sets.
This issue only happens when the lower bound of the x-axis range is <= .1000. This issue also only happens for certain data sets.

Workaround: Ensure the lower bound of the x-axis range remains above .1000 when using a logarithmic scale on the x axis.

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 03/23/2011
292544

Return
Deployed Measurement Studio network variable client programs cannot use LogosXT.
A LogosXT merge module is not available to redistribute the LogosXT components.

Workaround: Follow the steps in the help topic Deploying Measurement Studio Network Variable Applications to create a Measurement Studio network variable server deployment.

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 04/28/2011
297181

Return
Building a Measurement Studio ASP.NET Web Forms project fails on computers with United States Federal Information Processing Standard (FIPS) enabled.
This issue only exists in Microsoft Visual Studio 2005 and 2008. For more information on FIPS, refer to Microsoft KB 811833.

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 08/18/2011
297766

Return
The Instrument Driver Wizard crashes Visual Studio 2010 when trying to generate a wrapper for niHSDIO.fp.

Workaround: Open the .fp file in LabWindows/CVI, save the .fp file, and then use the Instrument Driver Wizard in Visual Studio 2010.

Reported Version: 2010 SP1    Resolved Version: 2012    Added: 08/18/2011
300030

Return
Excessive licensing dialog boxes display while evaluating Measurement Studio on a United States Federal Information Processing Standard (FIPS) enabled computer.
The Measurement Studio evaluation licensing implementation intends to display a licensing dialog once a day. However, if you are using a computer with FIPS enabled, you will see many licensing dialogs as you use the Measurement Studio evaluation version. Refer to Microsoft Support for more information on FIPS.

Workaround: N/A

Reported Version: 2010    Resolved Version: 2010 SP1    Added: 08/18/2011
301621

Return
The Measurement Studio Help is not uninstalled when Measurement Studio has been uninstalled.

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 08/18/2011
302132

Return
Cloning a ScatterPlot object does not clone the ProcessSpecialValues property.

Workaround: Manually clone the ProcessSpecialValues property.

Reported Version: 2009    Resolved Version: 2010 SP1    Added: 08/18/2011
306771

Return
In the Measurement Studio Help for Visual Studio 2010, links from Measurement Studio conceptual help topics to methods that have parameters and are not overloaded do not work.

Workaround: Search for the method name to view the associated function reference help.

Reported Version: 2010 SP1    Resolved Version: 2012    Added: 08/18/2011
309646

Return
When drawing very thick plot lines on a Measurement Studio .NET graph, the line can draw incorrectly.
Visible glitching can occur when the plot lines are thick enough.

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 08/18/2011
310916

Return
When using a Debug Deployment license, a dialog box states that there is "No License Available" when launching Visual Studio for the first time.

Workaround: Select Cancel. Visual Studio should continue to launch and work properly.

Reported Version: 2010    Resolved Version: 2012    Added: 08/18/2011
291290

Return
Distributing Measurement Studio applications to computers with User Account Control (UAC) enabled can result in an incomplete installation.
This may result in failures in various Measurement Studio libraries, such as TDMS, Network Variable, and 3D styles in the User Interface library.

Workaround: To resolve this issue, refer to KnowledgeBase 5KRERUQW.

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 08/19/2011
291489

Return
Running the HelpConfigurationUtility from a directory other than the one the utility is in causes the Help button to break.
For example, if you enter the full path to the HelpConfigurationUtility in the run prompt, pressing the Help button results in an exception.

Workaround: Run the HelpConfigurationUtility from the directory the utility is in.

Reported Version: 2010    Resolved Version: 2010 SP1    Added: 08/19/2011
291673

Return
Adding a Measurement Studio control to a Web User Control in an ASP.NET Web application project might result in an error.
The reported error states: The control cannot be displayed because its TagPrefix is not registered in this Web Form .

Workaround: Before adding any controls to your ASP.NET Web application project, add references to the NationalInstruments.WebForms assembly. You add references by selecting Measurement Studio»Add/Remove .NET Class Libraries.

Reported Version: 2010    Resolved Version: N/A    Added: 08/19/2011
292392

Return
Calling Filter.Reset can change the characteristics of the filter.
This issue applies to all Filter.Reset methods.

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 08/19/2011
292897

Return
Upgrading from Measurement Studio 2009 to Measurement Studio 2010 can result in failing distribution builds from other National Instruments software.
This issue only happens if you install the NI Measurement Studio 2009 Network Variable Update.

Workaround: If you are unable to build distributions in other National Instruments software, refer to one of the following KnowledgeBase articles:

Reported Version: 2009    Resolved Version: 2010 SP1    Added: 08/19/2011
294382

Return
64-bit TDMS applications might crash when reading properties.

Workaround: N/A

Reported Version: 8.6    Resolved Version: 2010 SP1    Added: 08/19/2011
295481

Return
When targeting a previous .NET Framework version in Visual Studio 2008 or Visual Studio 2010, the Measurement Studio Update Project References wizard attempts to update your project references to the latest .NET Framework version.

Workaround: When the Update Project References dialog box displays, select Do not show this prompt again for all projects in this solution.

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 08/19/2011
297106

Return
Uninstalling an application that uses network variable leaves behind the network variable assembly in the Global Assembly Cache (GAC).

Workaround: N/A

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 08/19/2011
298877

Return
Adding Measurement Studio .NET 3.5 assemblies to an ASP.NET Web site that targets .NET 4.0 results in incorrect dependencies added to the project.
The .NET 4.0 versions of the assemblies are added, and the .licx file is updated with .NET 4.0 licenses.

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 08/19/2011
307898

Return
The Measurement Studio License Status dialog box sometimes displays a button named "Launch Product" instead of "Evaluate Products"

Workaround: Select "Launch Products". The dialog box behavior is the same, regardless of the button text.

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 08/19/2011
284835

Return
You cannot de-select the Web Forms User Interface Control Library from the Add/Remove Class Libraries Wizard.
This bug exists for Measurement Studio 2010 SP1 and prior versions, and is fixed in Measurement Studio 2012 for Visual Studio 2008 and 2010. The bug still exists in Measurement Studio 2012 for Visual Studio 2005.

Workaround: Remove and re-add the NationalInstruments.Common.dll, NationalInstruments.UI.dll, and NationalInstruments.UI.WebForms.dll assemblies from the Visual Studio project.

Reported Version: 2009    Resolved Version: 2012    Added: 02/21/2012
296833

Return
The Parameter Assistant throws an exception and does not respond when browsing Source URL for NI DataSocket.
The Parameter Assistant does not close after the exception is thrown.

Workaround: Close Visual Studio and reopen it. The Parameter Assistant will open again, but will be functional.

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 02/21/2012
314617

Return
Measurement Studio ActiveX controls cause all controls to not anchor to right side of form.
This only occurs if the applications startup WindowState is set to Maximized.

Workaround: Start the application with the WindowState set to Normal, then programmatically change the WindowsState to Maximized in the Form constructor.

Reported Version: 8.1.2    Resolved Version: N/A    Added: 02/21/2012
317267

Return
If the Annotations do not have explicitly assigned axes, Annotations do not appear until the Windows Forms scatter or waveform graph is redrawn.

Workaround: Explicitly assign the XAxis and YAxis to new annotations as demonstrated in the code below. XYPointAnnotation anno = new XYPointAnnotation(); anno.XAxis = xAxis1; anno.YAxis = yAxis1;

Reported Version: 2010    Resolved Version: 2012    Added: 02/21/2012
317292

Return
The range fill for the Windows Forms Slide control shrinks when slider moves at run-time.

Workaround: Create two events handlers for the Slide control, MouseUp and MouseDown. Place the following code in each event: private void tank1_MouseDown(object sender, MouseEventArgs e) { tank1.PerformLayout(); tank1.Invalidate(); } The same code can be used for the MouseUp event.

Reported Version: 2010 SP1    Resolved Version: 2012    Added: 02/21/2012
322666

Return
Istantiating a ComplexDouble for the first time takes a longer than expected.

Workaround: N/A

Reported Version: 2009    Resolved Version: 2012    Added: 02/21/2012
328010

Return
Installing Measurement Studio 2010 SP1 for Visual Studio 2010 Express without integration support results in being unable to activate.

Workaround: To wrk around this issue, reinstall/repair Measurement Studio 2010 SP1 and select to install Integration Support. This will cause an installation error because Integration is not compatible with Visual Studio Express, but the installation will finish anyway. The assemblies should now be licensed.

Reported Version: 2010 SP1    Resolved Version: 2012    Added: 02/21/2012
332295

Return
The Windows Forms ScatterGraph displays a red "x" when out of memory, but does not throw an exception.
Under rare conditions, an OutOfMemory exception can occur while .NET asynchronously redraws a control.

Workaround: If you call the Graph.ClearData() method, the graph returns to a normal state.

Reported Version: 2009    Resolved Version: N/A    Added: 02/21/2012
335548

Return
Using the ZoomXY method on a Windows Forms ScatterGraph throws an exception when the y-axis is using a logarithmic scale type.

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: 2012    Added: 02/21/2012
337384

Return
Windows Forms Plot3DMesh causes an exception when run multiple times with a large number of points.

Workaround: N/A

Reported Version: 8.1.2    Resolved Version: N/A    Added: 02/21/2012
338809

Return
Windows Forms Graph axis label spacing is determined based the end labels, even if the end labels are not visible.
The spacing between the graph and the edge of control is automatically determined by the longest visible label or the end labels. Even when the end labels are not visible, they can affect the spacing.

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: 2012    Added: 02/21/2012
316607

Return
The WaveformGraph Plot with ProcessSpecialValues set to true hangs when double.PositiveInfinity is plotted or crashes when double.NegativeInfinity is plotted.
This can occur when calculating the MajorDivisions or MinorDivisions when AutoSpacing is set to false.

Workaround: Set AutoSpacing to true.

Reported Version: 2009    Resolved Version: 2012    Added: 02/22/2012
319689

Return
Modifications to the Range values in a Windows Forms graph using the dialog editor are not committed if only the Min value is changed.

Workaround: Move the cursor to the Max value before committing a change to the Range.

Reported Version: 2010 SP1    Resolved Version: 2012    Added: 02/22/2012
320362

Return
The Measurement Studio .NET XCOPY Deployment Files help topic for Visual Studio 2010 lists msvcm100.dll as a dependency.
The msvcm.dll library is not a dependency of Measurement Studio for Visual Studio 2010.

Workaround: N/A

Reported Version: 2010    Resolved Version: 2012    Added: 02/22/2012
338874

Return
If you set the WebForms InteractionMouseCursor property through the designer, the page does not save when using certain controls.

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 07/30/2012
344059

Return
Custom install locations are ignored when National Instruments Merge Modules target is set to the Module Retargetable Folder.

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 07/30/2012
349762

Return
The Windows Forms NumericEdit control does not initialize to a NaN value.

Workaround: Set the value of the NumericEdit control to double.NaN after the InitializeComponents method is called.

Reported Version: 2009    Resolved Version: N/A    Added: 07/30/2012
355871

Return
The ChebyshevLowpassFilter() documentation incorrectly lists stopbandRipple as a parameter instead of passbandRipple.

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: 2012    Added: 07/30/2012
360932

Return
The displayed scales for the Slide, Thermometer, and Tank WindowsForms controls do not accurately map to a value.
The value being displayed on the control may be slightly different from the actual value of the control. This is only noticeable if the control is very large, or if you are interacting with the control and want to set the value to the minimum or maximum.

Workaround: N/A

Reported Version: 2009    Resolved Version: 2012    Added: 07/30/2012
361842

Return
Icons for DataSocket URLs do not display with the DataSocket.SelectUrl popup.

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 07/30/2012
370422

Return
The HarmonicAnalyzer method in the Analysis Spectral Measurement library throws an AccessViolationException regardless of the input.
This only occurs when using the overloaded HarmonicAnalyzer(Double[], Int32, Double, Double, Double[], Double[], Double) form of the method.The exception is not thrown for the other overloaded forms.

Workaround: N/A

Reported Version: 2009    Resolved Version: 2013    Added: 02/24/2013
373901

Return
Appending data to a cloned WaveformPlot object causes a NullReferenceException to be thrown.

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: 2013    Added: 02/24/2013
384987

Return
The PropertyChanged event does not occur when the Plot property of a XYCursor changes.

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: 2013    Added: 02/24/2013
338802

Return
Calling the ClearData method on the Windows Forms DigitalWaveformGraph control a second time on an empty graph causes the horizontal scrollbar to disappear.

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 03/01/2013
373911

Return
Visual Studio crashes when the Instrument Driver Wizard attempts to load a function panel file (.fp) when an associated .sub file is encoded as unicode.

Workaround: Convert the .sub file to an ASCII encoding.

Reported Version: 2010    Resolved Version: 2013    Added: 03/01/2013

Document last updated on 3/14/2013

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).