[dfallon]

Same can be done for Data Grid columns too if needed: https://code.kx.com/insights/1.2/microservices/dashboards/datagrid.html#column

[dfallon]

Apologies,

In your stream setup you need to define [x].

The easiest guide for you is to perhaps look at the demo.q file inside the /sample/ directory which hosts the streaming examples which come with dashboards.  There are four streaming data sets which use [x]: book, book1Agg, book2Agg and stream.  If you use them as a template to your streaming example you should be able to set [x] as a filter.

You can test these four examples in the dashboard by using an FX symbol like EUR/USD.

Hope this helps,
Declan

[dfallon]

Yes, assuming you have in your streaming kdb query {[x] … … where Product in x}.  Then x as your Dashboard input is the value from the Product, “cgb10y” etc.  Your value for “x” should then be assigned to a view state parameter in Dashboards, so it can be used as part of a dropdown.

[dfallon]

Yes, you want to run the calculation in q before pushing it to Dashboards.

[dfallon]

You can also plot financial data with Dashboards Financial Charts component, with a range of chart types (candlestick, OHLC, line) 30 technical indicators and custom notes and overlays.  Users can then save their chart for sharing with colleagues.

For more information, including an explanation on the different indicators, check out code.kx.com.

 

[dfallon]

Hi MSHK,

If you havent already, take a look at the example we have for setting up a streaming process.

The screenshot you show for quote.bond has an input parameter exposed to Kx Dashboards, which is defined in your kdb streaming query.  More than one filter can be made available if required, but usually its a time series pull for a single asset so only one such query parameter is exposed.

Your streaming query should have the necessary bid and ask calculations, results of which are then pushed to the Dashboards.  The query handles the calculations returned in the Results pane when you Execute it.  There is a Key by dropdown as part of the streaming options for Dashboards (drawn from the data columns in your query), one of which should be time or date.

Dashboards only handles the filters from the query and the data key by, it doesnt do the underlying bid, ask calculation.

Take a look at our latest 1.4. release, which you download from here.   We have an upgraded version of Document Graph to help manage your queries and view states, this makes it easier for Dashboard users to work with large numbers of queries and/or view states without having to go through the component UI.

Thanks,

Declan

[dfallon]

Hi KS,

1.  You can drag to reposition the different sets of connections; I (mouse wheel) zoom out and then drag from the central viewstate or data source away from the cluster – in non-hierarchical mode – so it’s separate from the group and not overlapping. It will drift back to the central cluster but it may help isolate the problem.

2. There isn’t a search functionality for view states / data sources in the Document Graph.  There is a search in the Data Editor for queries and view state dialog for View States.

3. Given the complexity of your relationships – do you know which of your components is returning the deadlock? If so, copy that component, and paste it into a new Dashboard (ctrl+c / ctrl+v).  Then, look at the Document Graph.  Only the data sources and connections for that component will show in the Document graph, which hopefully will make it easier to find your blocker.

Thanks,

Declan

[dfallon]

Hi SK,

While Category will display your time points, it won’t account for missing time periods / non-sequential time data as the Time option supports.  Glad to hear the suggested solution worked.

Thanks,
Declan

[dfallon]

Hi SK,

Here is an example format with the sample data set; try this with your time data column and map the outputs to your view states:

 

mint: exec min time from dfxQuote; 
maxt: exec max time from dfxQuote; 
buffer: "n"$((maxt-mint) * 0.01); 
`min`max`buffer`bufferMin`bufferMax!(mint;maxt;buffer; mint-buffer; maxt+ buffer)

 

Thanks,

Declan