Skip to main content
  • Home
  • Product Ideas
  • The Timeseries Aggregate function for Power BI should have some additional parameters
Planned for development

The Timeseries Aggregate function for Power BI should have some additional parameters

Related products:API and SDKs
  • November 16, 2022
  • 4 replies
  • 138 views
crgomez13
Marcela Young
  • crgomez13
    crgomez13
  • Marcela Young
    Marcela Young
Glen Accardo
Active

Currently, the Power BI data connector contains a function to return timeseries aggregations and this function takes a source, start and end dates, and a granularity.  It then returns 13 columns of data.  My report only uses 3 of those columns: timestamp, timeseriesId, and Average.  With 3.4 million rows, this is a huge amount of wasted bandwidth and storage.  It also adversely affects the report performance to a small degree.

One possible solution to this would be to add a parameter to TimeseriesAggregate() to indicate which columns of data should be returned.  Not transmitting the data would save network bandwidth, reduce the size of the report, reduce the time required to load data, and improve the end-user experience.

4 replies

Arun Arunachalam
Seasoned Practitioner

Hei @Glen Accardo thanks again for reaching out regarding this and giving us valuable feedback. I will go ahead and add this to the backlog for us. I would also like to say that at the moment we are on a feature freeze for the powerBI connector due to the team being occupied with monitoring stabilisation within CDF but we should have a more open roadmap in the months to come.

Anita Hæhre
Seasoned Practitioner
Forum|alt.badge.img+1
  • Anita Hæhre
  • Head of Academy and Community
  • 590 replies
  • November 22, 2022
New→Gathering Interest
Anita Hæhre
Anita Hæhre
Seasoned Practitioner
Forum|alt.badge.img+1
  • Anita Hæhre
  • Head of Academy and Community
  • 590 replies
  • November 22, 2022
Gathering Interest→Planned for development
Anita Hæhre
Ville Ikonen
Active

Implementing this feature would be highly beneficial. If the native query into CDF would allow excluding unwanted columns completely from the downloaded dataset, it would reduce the downloaded data amounts greatly in most cases. It’s very typical to only need two or three columns from the query with the rest just being unnecessary fill that will get cut off in Power Query anyway.

Reply


Terms & ConditionsCookie Settings

Cookie Policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings