Resolving Missing Generic JDBC Connector in Sisense
This article addresses the issue where the Generic JDBC connector is not visible under available connectors for users logged in with a designer account in Sisense version 2023.6 or newer. This problem arises due to changes in the framework that affect the visibility of certain connectors for non-admin userResolving DBLink Issues in Sisense for Postgres Connections
This article addresses the issue of using DBLink with Postgres connections in Sisense. DBLink is a feature in PostgreSQL that allows users to connect and query data across different databases. However, users may encounter limitations when attempting to use DBLink within Sisense's custom import queries. This guide explains the issue and offers a solution to effectively manage data from multiple databases in Sisense.Resolving Missing Generic JDBC Connector in Sisense
This article addresses the issue where the Generic JDBC connector is not visible under available connectors for users logged in with a designer account in Sisense version 2023.6 or newer. This problem arises due to changes in the framework that affect the visibility of certain connectors for non-admin users.Resolving MongoDB Connector Performance Issues in Sisense
Resolving MongoDB Connector Performance Issues in Sisense Summary This article addresses performance issues caused by the MongoDB connector in Sisense, specifically related to the addition of an unnecessary parameter in queries and as a result, leads to inefficient query execution and overall system performance degradation. The article provides steps to resolve the issue and improve performance. Main Content Issue Description The MongoDB connector in Sisense may add an unnecessary parameter {"$not": {"$type": 2}} to queries translated from SQL to MQL. This additional parameter prevents the use of indexes in the execution plan, resulting in full table scans and significantly increased query times. This issue affects the initialization step of the EC build, causing delays in Cube builds and overall system performance failures. Steps to Resolve the Issue Identify the MongoDB Connector Version: Ensure you are using the MongoDB connector version 1.1, which is auto-installed as part of Sisense Fusion. Disable Mixed Type Filter: Use the parameter EnableMixedTypeFilter=0 to remove the additional filter {"$type": 2} from the queries. This can be done by adding the parameter to your MongoDB connector configuration. Verify Query Performance: After applying the parameter, monitor the query performance to ensure that the unnecessary filter is removed and indexes are being used. Use MongoDB Atlas or other monitoring tools to check the "Examined:Returned Ratio" for your queries. Upgrade MongoDB Connector: If the issue persists, consider upgrading the MongoDB connector to a version that supports MongoDB Version 6.0.16. Contact Sisense support to get assistance with the upgrade process. Troubleshooting Tips Check Indexes: Ensure that all required indexes are added to your MongoDB collections. Use MongoDB Atlas or other tools to review and optimize your indexes. Monitor Query Insights: Use MongoDB Atlas - Data Services - View Monitoring - queryInsights - profiler to monitor the performance of your queries. Identify queries with a high "Examined:Returned Ratio" and investigate further. Review Execution Plans: Analyze the execution plans of your queries to ensure that indexes are being used effectively. Look for any additional filters or parameters that may be affecting performance. Check out this related content: Academy DocumentationResolving Limited Column Retrieval in Sisense API Connection to Jira
This article addresses the issue where a Sisense API connection to Jira only retrieves native columns and does not include custom column fields. It provides a step-by-step solution to resolve this issue and ensure that custom fields columns are retrieved.Restoring missing connector
Sometimes connectors can go missing for some reason, leading to a breakdown in data connectivity. Restoring these connectors is crucial to maintaining a smooth data flow within your Sisense environment. This article describes the process of restoring a missing connector in Sisense; additionally, the added tutorial describes how to restore the missing connectors in the Sisense Linux environment.
“No Email Account” Google Adwords Connector Error
Question: When trying to connect to Google Adwords via the Elasticube Manager, you may run into the issue of not getting any email accounts you can choose from, or receiving an error saying there is no email account. Solution: Follow the below instructions to fix this issue: 1.) Open this link https://www.google.com/adwords/manager-accounts/ and create a Manager Account using a new email (or you can use an existing email). For details about the Manager Account, see here: https://support.google.com/adwords/answer/6139186?hl=en 2.) Go to your new Manager Account and click Account -> Link existing account. 3) Type in your existing Account ID and click “Continue”. 4) Insert your account name (it can be anything you want, and you can change it later) and click “Request Approval” to send a request. 5) Go to your existing account and open Account Settings. 6) Under the Account Access tab, you must accept the request from your manager account. In your manager account it will look like this: 7) Now connect to your account from Sisense (using the same credentials that you used before). You will see something like this: Now you can work with your account data in Sisense.
