Relabel the time dimension

Relabel the time dimension

As a model builder I want to have the ability to relabel the time dimension using a specific property/alias so that I don't need to create extra complexity and I can use all the benefits/functions of the time dimension to meet the users's requirements.

I will know this is successful if I could rename FY18 to YearXX and Jan1 to Month1, and so on.

Benefit : Adding extra lookups/modules doesn't always meet the visualisation requirements and adds complexity. Also, it will be possible to use the time dimension and all its functions even in situations where, for example, there is a strict requirement to "sanitise" the time dimension making it generic.

The content in this article has not been evaluated for all Anaplan implementations and may not be recommended for your specific situation.
Please consult your internal administrators prior to applying any of the ideas or steps in this article.
25 Comments
New Contributor

I would like to upvote this idea. We use the date format of 17-Jan-19 throughout our work and would like to be able to change all our dates in our Anaplan solution to this format.

New Contributor

In addition to relabeling months - it would be good to relabel the quarters as well.  Relabel the roll ups by Season (retail).  

Certified Master Anaplanner

Would also want to be able to rename to "Period 1" or "P1" and opt to show/hide the year. Will significantly reduce some models' complexity and remove many stories from backlogs.

New Contributor

Upvote, upvote, upvote! Great way to display data in the lingo that customers/users are used to.

Occasional Contributor

I'd like to gauge the views of people on this thread on a narrower consideration around Time period labels. While we understand the drivers for a more flexible scheme, e.g. to provide 'aliases' for Lists generally, we have feedback that some customers have specific concerns around the 'FY' prefix used in the labels for aggregate time periods, e.g. for 'Q1 FY19' or 'FY19'.

In cases where customers would rather not see the 'FY' prefix used (e.g. because their model doesn't actually represent a fiscal year), would the option to use a 'CY' prefix instead be of value?