JAQLine Plugin - Visualize Widget’s Queries

Follow
Avatar
Gideon B

*This plugin is officially supported by Sisense. You can find the latest version of this plugin on the Sisense Add-Ons page. 

Purpose/Benefits

Note: This plugin requires Sisense V6.6 and later. 

This plugin provides a visualization of the queries a widget performs towards an ElastiCube so you can understand which tables participate in the query, and which relationships between the columns of the tables are in-use by the widgets queries.

This plugin can help you troubleshoot your widget by displaying many-to-many relationships, and identify possible causes of slow query performance.

Steps

Step 1 - Add the Plugin

Download the attachment and unzip the contents into your C:\Program Files\Sisense\PrismWeb\plugins\ folder. If the plugins folder doesn't exist, create it.

Note that If you just created the plugins folder, you may have to restart the web server after unzipping the files.

Step 2 - Activate the Plugin

The JAQLine plugin is available for use by Administrator or Designer users.  It will not be visible to Viewers.

In order to activate the Jaqline plugin, click on the menu of the widget, and then click Analyze Widget JAQL.

A pop up window will display the query visualization. Click outside the window to close it.

3

Comments

41 comments

Sort by Date Votes
  • Avatar
    David Burke

    @Tim ah, that makes sense. I knew it had to be in tandem with another plugin but wasn't sure which one(s). I've also disabled the JAQline widget for the time being.

    1
    Permalink
  • Avatar
    Kevin Huilman

    After upgrading to 7.2.1 this plugin breaks emailing any dashboard/widget scheduled or manually. We tested it with it being the only plugin installed and it broke email. It does not matter what type of objects are on the dashboard. It can be just a table or just an indicator. If jaqline is enabled we get the "could not connect to the ElastiCube" error.  So I don't think this is an interaction with another plugin.

    Very disappointing, we get a lot of value from this plugin due to the complexity of some of our cubes.

    I do have a support ticket open about this.

    1
    Permalink
  • Avatar
    Chris Bridges

    I am experiencing the same issue as Kevin although I am using version 7.1.2.10076. Turning off the jaqline plugin is the only way for me to receive an email without the "could not connect to the Elasticube" error.

    1
    Permalink
  • Avatar
    Chris Bridges

    Also has anyone experienced a relationship that shows up as blank on both nodes? I'm not sure how to interpret this.

     

    0
    Permalink
  • Avatar
    Troy Dunn

    Doesn't appear to be available to the Data Designer Role

    0
    Permalink
  • Avatar
    Tim Friesen

    It is very clear that this plugin is NOT a priority for Sisense.  Do not use it unless you want dashboard exporting/emailing to be broken!  Might as well remove this from the plugins list.

     

    Tim

    0
    Permalink
  • Avatar
    Malinda Jepsen

    @Tim: Have you tried removing it for viewers? Or are all of your users designers?

    0
    Permalink
  • Avatar
    Stefan Castino

    Holy crap, I'm so glad I decided to look at the JAQL and it ended up here. Been driving myself crazy trying to figure out why emails were broken.

     

    Adding some keywords to make googling easier:

    "could not connect to the elasticube" email sisense

    0
    Permalink
  • Avatar
    Tim Friesen

    I can confirm that the latest update to this plugin (version 1.0.3 published Jan 18, 2019) has fixed the email issue!

    0
    Permalink
  • Avatar
    Dan Loewen

    The plugin was working fine with Sisense 7.3 but after upgrading to version 7.4 the plugin is showing a blank page with the following error in the console:

    TypeError: Cannot read property 'forEach' of undefined
    at o (/systemPlugins/main.74c5dc2a839a100f4fe8.js:20)
    at r (/systemPlugins/main.74c5dc2a839a100f4fe8.js:20)
    at /systemPlugins/main.74c5dc2a839a100f4fe8.js:20

    0
    Permalink
  • Avatar
    An Y

    Hi

    Wondering if anyone has a work around to this problem -

    We are experiencing a weird issue with this plugin conflicting with our dashboards on the recently upgraded 7.4 version. There is a 'Year' dashboard level filter which is Date type in the Elasticube. When an EDT time zone designer publishes the dashboard  with 2019  pre-selected  in  this Year filter it   is loading with 2018 selected for the  CDT time zone  users.

    We have identified below code in the .dash file as the problem . The dashboards are publishing with the Designer's time zone and 2019-01-01 date , and since CDT is an hour behind they are seeing 2018 in the Year. 

    With Plugin

    "filter": {
    "explicit": true,
    "multiSelection": true,
    "members": [
    "2019-01-01T00:00:00Z"
    ]
    }

    Without Plugin

    "filter": {
    "explicit": true,
    "multiSelection": true,
    "members": [
    "2019-01-01T00:00:00"
    ]
    }

     

    An

    1
    Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post