How to Troubleshoot UI Issues Using DevTools (HAR File & Console Logs)
If a webpage, dashboard, or widget isn't loading properly, encounters errors during exporting, importing, editing, or opening, or if buttons are unresponsive and error messages appear, you can use Developer Tools (DevTools) in your browser to diagnose the issue. This guide will show you how to: - Check the Network tab for failed requests. - Use the Preview and Response tabs to see details of errors. - Check the Console tab for other issues. - Save a HAR file to share with support.Mastering custom actions in Sisense: debugging and understanding payload properties
Custom actions extend the widget BloX's basic functionality. This article explains how to debug custom actions. Developing custom actions requires JavaScript programming experience and familiarity with the browser's developer tool.
REST Connector troubleshooting
Sometimes a user can experience difficulties while defining a REST connector. This guide will help to troubleshoot these connectors. Topics: REST connector prerequisites Timeout issue Logs to review Rest Connector Prerequisites: Below are the prerequisites that need to be reviewed before troubleshooting a REST connector: Make sure the config.json file is filled out correctly. You can find the relevant instructions here: REST API Reference Copy a connector's .dll file ('Sisense.Connectors.RestConnector.dll) from a working REST connector (for example: C:\Program Files\Sisense\DataConnectors\DotNetContainer\RestSamples\REST.LinkedIn.Connector) Make sure that the MongoDB driver is installed. The driver is essential to any REST connector since the data coming in from the REST sources is being temporarily stored in a MongoDB collection (see the following link for further instructions: Connecting to MongoDB). Timeout Issue: Knowing how long the API request takes to resolve using Postman or any other API development environment is mandatory to understand two things: whether the API itself is working and to determine if increasing the Sisense timeout values is needed. 1 - Connector SessionTimeout: There is a timeout parameter in the custom REST connector which checks if the data source is not responsive. In case the build exceeds this timeout, the build will fail. The default time is 30 minutes, which should be enough in most cases, but in case you suspect that the build fails because of this timeout, you can extend it. Below the steps to review this property: Open the "Sisense.Connectors.Container.Server.exe.Config" file which is located in "C:\Program Files\Sisense\DataConnectors\DotNetContainer". The parameter which needs to be changed is the following: <!--<add key="Server.SessionTimeout" value="60.0" />--> Uncomment it (remove the <!-- and -->) and change its value according to your needs. (as you can see, it is set in default to 60 minutes here). After modifying it, restart the Sisense.CLRConnectorsContainer service in order to apply the changes. 2- ElastiCube Server timeout: The Elasticube manager has its own ETL timeout which in some cases can cause this issue especially when its value is less than 7200. Below the steps to review this property: Open the "ElastiCubeConfiguration.xml" file which is located here: C:\ProgramData\Sisense\PrismServer. The parameter which needs to be reviewed is the following: Make sure that it is 7200 or larger. Save the file then restart the Sisense.ECMS service. 3- Table Timeout: There is also a way to force the table load Timeout. Below the steps: Open the "config.json" file which is located the connector directory Add the "Timeout" property as shown in the image (default value is 100000 (which is 100 seconds)) in every single table: Save the "config.json" if you edit it Restart the Sisense.CLRConnectorsContainer service 4- Large batch size: Having a large batch of data can also cause this issue. Below the steps to make sure that MaxDocs or FetchSize: Open the "config.json" file which is located the connector directory Make sure that MaxDocs and FetchSize properties are approximately the values shown in the image: Save the "config.json" if you edit it Restart Sisense.CLRConnectorsContainer service Logs to review: Reviewing the connector logs can give more insights about the ongoing issue. below the log path: C:\ProgramData\Sisense\DataConnectors\DotNetContainer\Logs Resources: Troubleshooting the Custom REST Connector
