System Insights displays the current health and state of your LYNQ application. This page is used by system administrators to troubleshoot and diagnose areas of LYNQ that are not functioning as expected. The SQL account that is specified in Settings, Database Settings must have SQL admin rights for this page to function properly.
Any values on the page that are highlighted red should be investigated for the continued operational health of LYNQ. This page provides at a glance a quick way to identify if there are any underlying SQL views that are not functioning correctly due to violation of key constraints. This is particularly useful when the database of the Enterprise Resource Planning application that LYNQ is connected to is set to a collation that is case sensitive. LYNQ is not a case sensitive application and therefore SQL views may not execute if there are duplicate keys returned.
One example of this is where two Product records have been created in the Enterprise Resource Planning application that differ on case. LYNQ would treat the value PRODUCTA and producta as a duplicated value. If duplicate keys are returned by the LYNQ SQL views, the application will be severely affected and, in some cases, partly or fully inaccessible by users. It is therefore important to understand these limitations and monitor the health of the application to ensure the application is fully operational.
Applies to: LYNQ 2019 system insights