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.

38 Comments
Miran
Super Contributor
 
Status changed to: Your support is needed
Rebecca
Valued Contributor
 
Status changed to: Under Investigation
Rebecca
Valued Contributor
 
Status changed to: Your support is needed
bradmalis
Occasional Contributor

I would like to upvote this idea.  I have a customer that uses a Feb - Jan fiscal year.  They label the fiscal year based on when it starts.  We are presently in FY 19, which started in Feb 19 and ends in Jan 20.  They would like to label Jan 20 as Jan 19 so they can see all of the months in the fiscal year with the same year on it.  There is a related topic, and i will upvote that as well.  

GrahamJordan
Contributor

Bump. We need this!

CommunityMember83188
Contributor

A great idea - this would life easier in no end of ways.

Alessio_Pagliano
Certified Master Anaplanner

@Manuela_Apostol , @usman.zia , @Yugnesh.Patel , @MagaliP , @Rich.Buttivant  sorry for the sneaky tagging. Have you seen this sort of requirement and finding the workaround not ideal ? If you agree this would be helpful...could you help with your kudos ? Feel free to do the same with me, whenever needed! 

 

Thanks,

Alessio Pagliano

usman.zia
Community Boss

Hi @Alessio_Pagliano 

 

You have my support! 

It would be useful to see this sort of functionality! 

Alessio_Pagliano
Certified Master Anaplanner

@usman.zia , thanks Boss! That Community Boss badge works very well : you made the kudos jump from 6 to 16 🙂 Nice!

Manuela_Apostol
Certified Master Anaplanner

HI @Alessio_Pagliano.,

 

This is quite an interesting topic but I have mixed feelings about it and I don't see immediately the added value of this enhancement. Is true that is not always possible to use TIME and are some challenges we face as model builders, though the workaround with creating Time Dimension List is at hand and there are not many disadvantages. I would like to know the opinion of our community guru @DavidSmith

 

Cheers,

Manuela 

Rebecca
Valued Contributor
 
Status changed to: Under Investigation
Rebecca
Valued Contributor
 
Status changed to: Under Investigation
DavidSmith
Community Boss

@Manuela_Apostol Thanks for the mention

Using dummy timescale is an obvious workaround, but I think the "re-labelling" concept is something much wider.  There have been a number of similar posts, but for me, the ability to have aliases for all lists would be of great benefit; not just for time

So a Display name concept for all lists, time, versions, modules etc

this would allow total flexibility, dynamic labelling as well as dealt with the language support challenges

It is an idea I have and will discuss with our product team

David

Alessio_Pagliano
Certified Master Anaplanner

@Manuela_Apostol and @DavidSmith , thanks for your comments.

 

David, while you discuss this with the product team, would it be possible to obtain an update on the Versions list ? Subsets/Production data and selection as format would be quite helpful. There are a few ideas for this, all asking pretty much the same - I'm assuming this is the "master" idea ?

 

Thanks,

Alessio 

DavidSmith
Community Boss

@Alessio_Pagliano 

Yep, I had a discussion last week and we have another next week to discuss these topics.

You'll appreciate the number of conflicting priorities we have, but I am pushing the case

David

Alessio_Pagliano
Certified Master Anaplanner

Thanks @DavidSmith , much appreciated !

karl.mcphee
Contributor

This idea is a request from one of our customers for more date formatting options within the Anaplan platform.

 

Currently, we have no control over the formatting of a date formatted line item apart from the browser locale setting which displays the date in a form of 13/07/2019 or 07/13/2019.

 

The request is to have more control here to allow formats such as those listed below to be possible:

Monday, 13th Jul 2019

13th Jul 2019

13th July 2019

etc

 

Key ask is to be able to see the month in a text based format rather than numerically natively in the platform without having to invoke workarounds of splitting date into numbers and then recombining into text strings.

 

DavidSmith
Community Boss
Miran
Super Contributor
 
Status changed to: Your support is needed
Samantha
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 change all our dates in our Anaplan solution to this format.

Samantha
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.

eschera
Group Leader - Employee

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

allison_slaught
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.

matt_anthony
Contributor

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

stephen.brook
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?

KeisukeT
New Contributor

This is great idea, also would like to upvote!! my core customer really need this enhancement. I think we should have options to adjust local customer business practice.

RieS
New Contributor

We need this function. Please, please, please...!

Gwen.pryor
Regular Contributor
 
Status changed to: Not Planned
Alessio_Pagliano
Certified Master Anaplanner

😞

david.savarin
Super Contributor

So is this abandoned or was it rebooted because of the recent status changes ?

I want to upvote that idea as well.

Not a dealbreaker, but the aliasing of time dim would be a good "nice to have"

DavidSmith
Community Boss

@david.savarin 

We are releasing functionality to allow you to change the 2 letter prefix for the time labels - This is due in August

 

On the wider relabelling question, I want to look at the alias concept across the whole model; I think there would be benefits for "labels" for all model structures, not just the timescales (although we could start there)

 

David

Alessio_Pagliano
Certified Master Anaplanner

I'm a super fan of wider labels/aliases across the entire model. Glad to hear it's still on the radar!

david.savarin
Super Contributor

Awesome that we can now relabel years labels

vicky_ascencio
Occasional Contributor
 
Status changed to: Delivered
Alessio_Pagliano
Certified Master Anaplanner

Hi @DavidSmith ,

What's just been delivered is certainly a good step forward and I can see how it would help some customers.

However, further to my original idea I'm also attaching a diagram to help clarifying this idea further.

Anaplan_Time_Idea.JPG

Could you confirm if this is already in the pipeline and/or if I misunderstood what's been delivered ?

 

@vicky_ascencio  , I noticed you changed the status of this idea to "Delivered", depending on what David says I would amend it accordingly.

 

Thanks,

Alessio Pagliano 

Hayk
Frequent Contributor

This is smth which'll help us a lot! 

We use custom week labels, which is critical for business. It makes us build intermediate modules on real timescale to run time functions and map back to fake timescale reports. 

 

Thanks,
Haik

mnishibu
New Contributor

Hi @david.savarin  san,

 

This is Nishibu from Japan.

 

Time scale format is fixed as "Mon YY" when uses Month scale. Most Japan customers are not familiar with that format. Then relabel functionality is definitely valuable for many Japan customers.

 

Thanks

Buhagim
New Contributor

Guys - we definitely need this ability / flexibility for our corporate reporting.

I call it Aliasing - but relabelling is equally valid description. Think about it like this:- 

In a corporate world we are dealing with two or three types of stakeholder. 

  1. Real calendar time users require the columns of information to appear by month so they might see progress across time - perhaps multipe years. This appears to be the default time line that Anaplan has delivered. 
  2. Financial reporting is different.
    • The management and accountants see reports independent of the calendar month and are fixed in a corporate reporting time base. i.e. if the organisations accounts are from April to march then they would see columns of data by period (P1 equating to April, P2 to May etc).
    • This means quarters are tied to periods based on the financial year start i.e. Qtr1 is P1,2,3 not Jan, feb and mar.
    • To add to this they require the financial year to be included in the heading alongside the period. P1 by itself is meaningless unless it also states P1 FY 19/20 or P1 FY20/21. This format is the one I urgently need the system to auto produce. 
  3. Dynamic headings - similar to item 2 BUT....
    • Many calculations refer to comparisons with prior period or prior year - which is fine if your report is fixed in time i.e.  i report in May so prior period is Apr and next period is |Jun.
    • However when I report in June my prior period is May and next period July. The time headings should reflect this and change to Pn FY YY/(YY+1) without having to modify a static text header. I need the system to sort out the headings correctly based on the Pn YY/YY format and be able to change the heading automatically under programme control. Similar to a date field in Excel where you increment the period and Year in teh heading using an equation 

For what its worth the corporate time base above would be the standardised one used across the model - so we could set it as a systems policy - unlikely that we would use both types 1 and 2.

 

Hope this gets the point across - let me know if you need more 

Mike