Dear visitor, despite the COVID-19 outbreak, our team continues operating at full speed.

Also, here is the form where you can apply for a special discount and we will contact you with possible options. Stay safe and continue achieving your business goals.

Fill the form
Get Free Trial
Get Free Trial

[Feature proposal] Allow filtering by “Top” or “Bottom” on rows and columns

Answered
Projet TCD asked on February 28, 2020

Hello,
This is a feature proposal (not request) that could be nice to have in Flexmonster’s pivot table.
Existing feature:
As of now, it is possible to filter values with a query objet on criteria top ou bottom (https://www.flexmonster.com/api/value-query-object/).
However, these criteria do not exist in other query objects (Number, String, Date, Time).
 
Proposed feature:
Adding support of “top” and “bottom” conditions on Number, String, Date and Time query objects.

  • Number: X top/bottom values
    • e.g.: { “top”: X }
  • String: X top/bottom values (by alphabetical order)
    • e.g. { “top”: X }
  • Date: Values corresponding to X latest/earliest “day”, “week”, “month”, “quarter” or “year”
    • This filter could return more than X values if “week”, “month”, “quarter” or “year” are selected
    • e.g. { “top”: “Xy” } with “Xy” being:
      • “Xd” – X days. Example: “5d”
      • “Xw” – X weeks. Example: “5w”
      • “XM” – X months. Example: “5M
      • “Xq” – X quarters. Example: “5q”
      • “Xy” – X years. Example: “5y”
  • Time: Values corresponding to X latest/earliest “second”, “minute”, “hour” or “day”
    • This filter could return more than X values if “minute”, “hour” or “day” are selected
    • e.g. { “top”: “Xy” } with “Xy” being:
      • “Xs” – X seconds. Example: “5s”
      • “Xm” – X minutes. Example: “5m”
      • “Xh” – X hours. Example: “5h”
      • “Xd” – X days. Example: “5d”

 
Goal of the feature:

  • Allow more dynamic filtering of rows and columns: the same filtering result can be achieved by manually checking/unchecking values in the row/column filter, but since the members themselves are stored in the filter, it means it won’t necessarily be correct when data is added/updated/removed.
  • Allow display of most recent data available when using dates as a dimension, even when the data is in the past (or at an unknown period): again, the same result can be achieved by filtering dates (greater than, last X days, …) but they rely on specific dates to work so they need to be changed every time there is a change in the data.

Best regards,
 
 

3 answers

Public
Illia Yatsyshyn Illia Yatsyshyn Flexmonster February 28, 2020

Hello,
 
Thank you for reaching out to us.
 
Your suggestion on adding such a feature sounds reasonable, and we have added the request on the implementation of the described functionality to our backlog.
 
We will keep you posted with any updates on this point.
 
We are grateful for sharing your ideas with our team. Do not hesitate to contact us in case any additional proposals or questions arise.
 
Best regards,
Illia

Public
Projet TCD May 15, 2020

Hello Flexmonster team,
Is there any new information on this feature for the near future?
I’d also want to add the suggestion, for the sake of completeness, that this feature could include the “not_top” and “not_bottom” conditions for all query objets (i.e. the opposite of the proposed feature above).
Thank you and best regards.

Public
Illia Yatsyshyn Illia Yatsyshyn Flexmonster May 15, 2020

Hello,
 
Thank you for writing to us and sharing your ideas.
 
Our team would like to kindly inform you that your request is placed to our backlog. However, our roadmap is full at the moment. We have complemented the request with your latest idea about “not_top” and “not_bottom” filtering.
 
We will notify you as soon as something is changed on this point.
 
Do not hesitate to contact us in case additional suggestions arise.
 
Best regards,
Illia

Please login or Register to Submit Answer