[kieran]

There is 2 simple options here

1) If you have a license, then make sure that you have this located in the root of your dashboards install

2) Alternatively, download the latest version of KxDashboards and replace the go.q_ from the latest with your install

 

 

If you need any more help here then please let me know

Kieran

[kieran]

{[filterString] .dfilt.apply[dfxQuote; filterString] }

 

If you have a set of the Datagrids with the same query like above and you :

1) set the “Filtering” property to “Advanced Column Filter”

2) set the “KDB filter string” property to same shared viewstate

 

Then if you update a column filter in table 1, and go to table 2, then the same filter will be applied

If you then change the filter in table 2, this filter will be applied to table 1

 

 

If you need any further here, just let me know

[kieran]

Hey,

 

There is a bug here , that we are looking into.

I would recommend using ChartGL here if you can in the meantime and if you have any questions on how to config this just let me know

[kieran]

Hey CJ,

 

 

To give a user access to upload, you can assign them following entity :  “configurationAdminAPI” and this will resolve the issue.

 

For more info, here are the docs on API permissions -> https://code.kx.com/platform/controlui_api_permissions/

[kieran]

Hi CJ,

most likely these issues might be caused by the Content Security Policy (CSP) on the server.

If you are using chrome (press ctrl+shift+i) to see the error console . If there is an error here, could you post a screenshot here and we can then point you in the right direction

[kieran]

Thanks for sharing, Wendy

 

 

[kieran]

We will add a fix to our next release to allow the “Force Reset” option on static queries.

 

In the meantime, to work around this

1. switch to polling query

2. click on “Force reset”

3. switch back to static query

4. save and refresh – “Force Reset” will now be turned on in static queries

 

 

[kieran]

Currently we do a major release each quarter and a minor release each month.

For each quarter release – we have started to add our release notes to our “Latest from KX” blog section : https://community.kx.com/t5/Latest-from-KX/bg-p/news/label-name/release%20notes (you can additionally subscribe to these release notes)

The next quarter release will be at the end of the month (2.1.0) I can ensure that we add the full list of fixes in here too going forward.

[kieran]

Hey,

It seems like you are using the correct properties here, I have attached a working demo  below just to confirm the database properties. (just change the dropdown selection to change the database columns)

 

In terms of potential issues, a first port of call is to check the console to see if there are any errors being returned by the queries that may potentially cause an issue.  To open up console press control + shift+i

 

 

[kieran]

I have added an example below of how to get the distinct set of results (using _.uniqBy) . For more information on this function or any other useful functions please have a look at : https://lodash.com/docs/4.17.15

function (source, callback) {
    var result = {
      "columns": ["exchangeName"],
      "meta": { "exchangeName": 11},
      "rows": []
    }
    result.rows= _.uniqBy(source.rows,"exchangeName");
    callback(result);
}