Skip to main content
darkknight
Expert ⭐️
September 21, 2015

Reports 2.0: Ability to rename the labels on the Legend of a report

  • September 21, 2015
  • 19 replies
  • 190 views
We have data streams coming in via MDA with names that, while applicable, are not ideal for reporting purposes.

Would like the ability to rename labels on a Report legend. i.e. in attached example, I would like to be able to change "docs-view" to read "Documentation" when I create the report in Reports 2.0.

    19 replies

    darkknight
    Expert ⭐️
    March 29, 2018
    We have Custom Fiscal Year values that are set in Salesforce.  Need some sort of an override capability in reports/graphs.

    Jeff Kirkpatrick
    dan_ahrens
    Expert ⭐️⭐️⭐️
    May 8, 2018
    I wanted to circle back on this one, Jeff. Since the aggregations for data in the "By:" (not the "Show Me:") part of the report is grouping by the names of the actual data in the source data, what did you have in mind related to the renaming? 

    Here's where I see a potential concern - while you might be able to rename the data labels that appear in the filtered data set (for example, if you are aggregating by month and look back 90 days, you could rename May, April and March to something else) for the current view, since the filters are usually dynamic, you'd have a maintenance headache to make sure any date movement or new fields that appear in that data set don't result in labels that don't have your customizations applied. 

    What are your thoughts on that challenge? Any changes to the data sets (or even validation constraints by future admins) would break this custom labeling. 
    VP of Customer Success at Forcepoint
    darkknight
    Expert ⭐️
    May 8, 2018
    You raise a really good point.  I guess it would not work as well for reports that shift due to date ranges.  
    Jeff Kirkpatrick
    dan_ahrens
    Expert ⭐️⭐️⭐️
    May 8, 2018
    I was thinking both date ranges and any data set where the values in the column used for the "by:" grouping could potentially change. If you can't control the possible values in that data column then it probably is a bad idea to try and create custom labels. 
    VP of Customer Success at Forcepoint
    darkknight
    Expert ⭐️
    May 9, 2018
    Dan - this may need to be another post, but the issue I'm running into here in the example above is because - according to support - our SF fiscal year settings are configured with a Period prefix of "Period."

    I'm not sure what that has to do with aggregating a Case::Closed Date, but we cannot change the Fiscal settings (our fiscal months apparently do not follow the calendar month).  

    Is there a reason the aggregation has to rely on the Fiscal settings? 
    Jeff Kirkpatrick
    dan_ahrens
    Expert ⭐️⭐️⭐️
    May 10, 2018
    Hi Jeff, sorry but I'm probably not going to be able to help on this one as it sounds like it goes deeper than my expertise. You mentioned that you have a case opened already? Hopefully L2 can provide some guidance.
    VP of Customer Success at Forcepoint
    darkknight
    Expert ⭐️
    May 10, 2018
    I did but it was closed because they said it was caused by the Fiscal Year settings. I just don’t understand what correlation Cases have to Fiscal settings.

    There is likely an enhancement request here but I will reopen case.
    Jeff Kirkpatrick
    darkknight
    Expert ⭐️
    May 14, 2018
    Support came back and determined that if you use Last N Days = 90, it displays MMM-YY, but for some reason Last 90 Days uses the Fiscal settings.

    Very strange.
    Jeff Kirkpatrick
    February 13, 2019