Hi,

ods-adv-analysis can replace ods-aggregation for many usages, as you can count/group/aggregate etc…

Can you give me an example of limitation you encounter please ? We’ll maybe find a workaround.

Hi Frederic,

Thank you for your response!

The issue I’m facing specifically occurs with large datasets that exceed 20,000 elements. Otherwise, the ods-adv-analysis widget works perfectly.

Here’s the code I’m currently using:

<div ods-adv-analysis="analysis"

     ods-adv-analysis-context="mycontext"

     ods-adv-analysis-select="SUM(value) as power"

     ods-adv-analysis-group-by="hour">

     <div ods-subaggregation="analysis"

          ods-subaggregation-serie-pmax="MAX(power)">

          {{results<0].pmax}}

     </div>

</div>

However, when I try to add something like {{analysis.length}}, I notice that the length never goes beyond 20,000.

Thanks again for your help!

Hi everyone, 
I am struggling also with the number of records in an ods-adv-analysis. 
If I don’t specify a limit, I have only 1 record : 

ods-adv-analysis="maintenances"

ods-adv-analysis-context="kaptamaintenance"

ods-adv-analysis-select="nom,date_end,cause,nbchgtsonde,nbchgtgsm,nbchgtbattery,nbnettoyage,nbchgtsim,chgt_freq"

kaptamaintenance :

<br />

If I specify a ods-adv-analysis-limit="100" then I have 100 records 

If I specify a ods-adv-analysis-limit="1000" I don’t have anything: 

Can you help me with this?

@Antoine , indeed, I understand now as you make a 2 step aggregation with ods-subaggregation widget. And therefore you suffer from this limit. 

The big problem here is not the limit from the API. It’s the fact that the API don’t provide a two step aggregation that would suits your need. 

Because when you do this kind of trick, you must keep in mind that you’ll download the entire output from the API (20 000 rows) and then, parse them and compute another aggregation. 

It the API limit would be 100K or even with no limit, the page would be frozen and the experience would be very slow or even too long to load for the user. 

So this kind of usage should be avoided and we often need to find another way to proceed. 

In your case it’s clearly a limitation of the API, and the only way to resolve this would be to have an intermediary dataset based on the first step of aggregation : 1 record would be the SUM(power) by hour for 1 year of data for exemple (as in one year you have 24*31*12 hours, that is less than 20 000).

Or you limit your dashboard to get the biggest hour for only 1 year, by filtering your context that perform the analysis. 

I clearly understand that it’s not ideal, I shared this topic internally and we have these usages in mind regarding API evolutions. 

@Guillaume Perrin-Fabre ods-adv-analysis has two limits depending on the type of query.

When you list items, as it relies on /records endpoint, you have the 100 hits limitation. Asking for more will return an error from the API (I encourage you to always have the console opened to see the 400 errors in the console or network tab and read the API error as it’s explicit)

When you perform a groupby, you go through the aggregation endpoint/feature and therefore you’ll have the 20K hits limitation.

In your case, if you want to list and go beyond the 100 limit, add a groupby with all the fields listed in the select clause, it will output the same thing, but without the limitation. 

Super clear, Thanks @frederic.passaniti!

Thanks @frederic.passaniti , your answer is much appreciated!
I understand that 2-step aggregation is indeed tricky, and I hope to see the API enhanced for this type of usage.

For now, I will explore your suggestion to create an intermediate dataset.