Hi everyone,
When using a trended table parameter from a protocol in the Line and Area Chart, it needs to be filtered by element ID and index. We achieved this by adding a filter from another component, which gave us the correct data.
However, when there are many elements (from the selected protocol), the dynamic filtering introduces a delay in loading the trend graph. This delay comes from the slow query of the filter component.
Is there a way to apply a filter using an Ad hoc data source, since it performs much faster than a query built entirely in LCA? Or are there alternative methods to efficiently filter trended table parameters for the Line and Area Chart component?
Hi Alija,
It is possible to expose Elements & Parameters from an Ad Hoc Query, but not Indices. I suggest you create an Ad Hoc source that directly returns the Parameters and use that as data in the Line & Area Chart component instead of filtering on the data from the query.
You can find an example in the docs on how to link rows in a query to DataMiner objects.
My suggestion is to remove the protocol parameter as data from the chart and replace it with a parameter coming from your query component. This removes the need for the index and element as a filter since you can already specify this when creating the metadata for the query rows. I currently do not see a better solution because Index metadata isn't supported (yet).
Hi Wout, Thank you for the answer. This looks good, except that I need index too, and I don't see I can get any improvement with this.
As already mentioned, slowness in my case is caused by a component query that gets me the index and element id for filtering, and not actually the data used in the Line and Area Chart.