SystemLink 2021 R2 Known Issues

概览

This document contains the SystemLink known issues that were discovered before and since the release of SystemLink 2021 R2. 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.

Bug Number

Legacy ID

Description

Details

211182

Using the browser navigation buttons does not correctly change a query

On pages with a query panel (Assets, Calibrated Assets, Reports, etc.), the browser back button does not work as expected. When a user presses the back button, the URL in the browser changes, but the filters do not.

Workaround:

Remove the filter using the X button next to the property selection field instead.

Reported Version:

SystemLink 19.5

Resolved Version:

N/A

Added:

Feb 27, 2020

1077209

Packages disappear from grid when viewed in Safari full screen mode

Package Repository application fails to display packages in the feed's detail view when done from Safari in full screen mode.


Workaround:

Use a different browser such as Chrome or take Safari out of full screen mode.

Reported Version:

SystemLink 2020 R3

Resolved Version:

N/A

Added:

Dec 10, 2020

1038431, 1379439

Stored test results can be sent to the incorrect server when client registration is changed while forwarding is in progress

If the store & forward plugin is already loaded and forwarding steps, it continues to forward to the original server connection even if the server is changed.  It will not switch servers while there are current transactions on disk and still successfully forwarding them.  Since simply switching the master does not invalidate the old API key, then if the server is still accessible, the forwarding plugin does not know that it should switch to the new master.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink 2020 R2

Resolved Version:

N/A

Added:

Dec 11, 2020

1350133

Windows login account cannot be used as TDM User Account

Logging into the Windows SystemLink servers with different user accounts can create issues with TDM services like DataFinder in case when one of these login accounts is also being used as SystemLink TDM User Account.

Workaround:

Assign a specific user/account to SystemLink TDM services.

Reported Version:

SystemLink 2020 R4 | SystemLink 2021 R1

Resolved Version:

N/A

Added:

Apr 27, 2021

1531598

Systems Browser - Build Query slide out becomes unresponsive after removing blank query item

When using the Build Query slide out to create a filter from the Systems Browser, it is possible to get into a partially unresponsive state. One way to get into this state is via the following actions:
  1. From the Systems Management -> Systems page, click the filter icon to open the Build Query slide out
  2. Press the blue "+" button to add a new query item
  3. Delete the new item via the "x" button on its right
  4. Click into a field in a query item and note that it no longer auto-populates and the rest of the item becomes unresponsive
To confirm this is the behavior you're seeing, open your browser's development tools and navigate to the console tab. Repeat the steps that caused the failure and you should see the following output:
Error TypeError: Cannot read property 'dataValue' of undefined
at HTMLElement._openEditorByFieldType (main.767261e...js:106)
at HTMLElement._openEditor (main.767261e...js:106)
at HTMLElement._clickHandlerFilterButton (main.767261e...js:106)
at HTMLElement._clickHandler (main.767261e...js:106)
at HTMLElement._documentDownHandler (main.767261e...js:106)
at HTMLDocument.d (main.767261e...js:106)
at f.dispatch (main.767261e...js:106)
at l.invodeTask (polyfills.af259fe...js:1)
at Object.onInvodeTask (main.767261e...js:106)
at l.invokeTask (polyfills.af259fe...js:1)

Workaround:

option 1: Press the blue "+" button again to add a new item. All items in the query should become responsive again. Delete any unused query items once you've configured the query fully.
option 2: Press the "Cancel" button on the slide out and recreate the desired filter, avoiding the steps that caused the failure.

Reported Version:

SystemLink 2021 R2

Resolved Version:

N/A

Added:

Jul 19, 2021

1523458

The 'Edit Grid' slide-out is empty when a non-existent property is selected

When the Systems grid is configured to group by a custom property that is not present on any visible system, the 'Edit Grid' slide-out can become empty and un-configurable. This can happen by deleting a custom property or by applying a filter that excludes all systems with the property being used for grouping.

Workaround:

To resolve the issue, update to SystemLink 2021 R2.1

Alternatively, you can identify the property in the grid that no longer exists, and ensure it is present on a visible system. This will allow you to edit the grid configuration and remove that grouping from the configuration.

Reported Version:

SystemLink 2021 R2

Resolved Version:

SystemLink 2021 R2.1

Added:

Aug 13, 2021

1706828

DataFinder stopped because SL TDM Database Service crashed

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink 2021 R2

Resolved Version:

SystemLink 2021 R2.2

Added:

Nov 24, 2021

Final Time Issue Listed

Issues found in this section will not be listed in future known issues documents for this product.

There are currently no issues to list.

Additional Resources

Explore Support Content and Product Documentation 

 

 

Ask the NI Community

 

 

Request Support from an Engineer

 

A valid service agreement may be required, and support options vary by country

 

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