Trend reports using an arbitrary date field Hot

by David Matsumoto on March 27, 2015

While submit date works for many cases, it doesn't work in all scenarios where other date fields like close date or a user created field might fit better. Reports like tasks completed in a specific month would become possible. An arbitrary data field would remove all restrictions from the functionality.

  • Ideas

    Target Release
    1HCY'17
  • Please login to view any attachments.

  • After reviewing with the team, we agree that implementing the first part of request, i.e. have ability to specify different date field to use instead of 'submit date'. That said, the broader request - i.e. add date fields to drop-down lists for selection of 1st/2nd fields - could lead to difficulties in presentation. In general, a trend report is supposed to have (relatively) limited number of values on the left (/rows) with unlimited time-line going to the right. Having a large vertical scale with the same long array of numbers/dates as for horizontal firstly may not make sense, and secondly could cause some memory/performance issues with the browser. I will reopen the request for the original idea and we'll consider it for a 1HCY'17 release of SBM.
    David J. Easter Commented by David J. Easter September 27, 2016
    #1 Reviewer  -  

    After reviewing with the team, we agree that implementing the first part of request, i.e. have ability to specify different date field to use instead of 'submit date'. That said, the broader request - i.e. add date fields to drop-down lists for selection of 1st/2nd fields - could lead to difficulties in presentation. In general, a trend report is supposed to have (relatively) limited number of values on the left (/rows) with unlimited time-line going to the right. Having a large vertical scale with the same long array of numbers/dates as for horizontal firstly may not make sense, and secondly could cause some memory/performance issues with the browser. I will reopen the request for the original idea and we'll consider it for a 1HCY'17 release of SBM.

    Exactly what I'm looking for!
    Phil Bustin Commented by Phil Bustin September 22, 2016
    Top 10 Reviewer  -  

    Exactly what I'm looking for!

    As discussed on ichange, I think this is very hard to implement via advanced reporting. The problem is that the results of advanced reporting cannot be used in trend reports. Create an advanced report whose result is displaying a trend in a distribution report is very hard (and quite inconvenient, since the modifying the date range or the grouping (week/ day) would imply modifying the xml on the server side).

    So IMO, it is inaccurate to consider this addressed. If you consider there is enough demand to address it, you could either enable trend reports on auxiliary tables (therefore being able to use the result of an advanced report to trend on), or make the user able to choose the date field in the trend report.
    David Berner Commented by David Berner September 21, 2016
    Top 10 Reviewer  -  

    As discussed on ichange, I think this is very hard to implement via advanced reporting. The problem is that the results of advanced reporting cannot be used in trend reports. Create an advanced report whose result is displaying a trend in a distribution report is very hard (and quite inconvenient, since the modifying the date range or the grouping (week/ day) would imply modifying the xml on the server side).

    So IMO, it is inaccurate to consider this addressed. If you consider there is enough demand to address it, you could either enable trend reports on auxiliary tables (therefore being able to use the result of an advanced report to trend on), or make the user able to choose the date field in the trend report.

    After review, we believe that this idea will be possible using the Advanced Reporting capability being introduced in SBM 11.0. I'll put this feature "Under Consideration" to show it's targeted for that release. SBM 11.0 is estimated to release by the end of the year, likely by early November.
    David J. Easter Commented by David J. Easter September 16, 2015
    #1 Reviewer  -  

    After review, we believe that this idea will be possible using the Advanced Reporting capability being introduced in SBM 11.0. I'll put this feature "Under Consideration" to show it's targeted for that release. SBM 11.0 is estimated to release by the end of the year, likely by early November.

    David, the break down of weeks/months/etc needs to be by any user created date field. Currently, the weeks/months are only by Submit Date. The drop lists (single selection) for 1st/2nd Field do not offer a date field. Per help - "The list contains Binary/Trinary, Single Relational, Single Selection, and User fields".

    Really need to have these reports by a user created date, in addition to Submit Date.

    Hope that helps...

    Thanks!
    Russell Ilgenfritz Commented by Russell Ilgenfritz July 08, 2015
    Top 500 Reviewer  -  

    David, the break down of weeks/months/etc needs to be by any user created date field. Currently, the weeks/months are only by Submit Date. The drop lists (single selection) for 1st/2nd Field do not offer a date field. Per help - "The list contains Binary/Trinary, Single Relational, Single Selection, and User fields".

    Really need to have these reports by a user created date, in addition to Submit Date.

    Hope that helps...

    Thanks!

     
    View all user comments
     

PrintEmail

Recent Tweets