nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Time Scale changes

PrevContributor

Hello, Please do let me know if there a way to rename the Time period Label of Year? For eg FY2015, FY2016 etc. to 2015 or CY2015. Thanks, Suneesh

Accepted answers

All comments

PrevContributor

Hi Suneesh,

As of right now there is no way to change the standard date format display. However, a workaround would be to use a formula that reformats based on the result in the timescale column. Unfortunately that wouldn't replace the standard timescale column, feel free to let me know if you'd like more details on this workaround approach.

-Chris Weiss

Alessio_Pagliano

Hi,

I would find helpful to see an example/more details on this approach, please .

Thanks,

PaulRitner

Hi,

There are two contexts for examples:

Where we don't like the column headers, or,
Where we have a line item that reformats a date or time period value

For item 1, the only way to change the format of the native timescale column header is to use a false time dimension (for the related reports and map Anaplan time periods into the false time periods). In this case, it might be addressed as follows:

Create a list named TimeList (or something)
- Call the items in the list whatever you need. For example
  - Total
    - Jan
    - Feb
    - Mar
    - etc...
- For each item in the list, we will either map the item to an explicit period, or calculate the mapping if the list is used in conjunction with another dimension (such as native Anaplan time in years)
  - If explicit reference, just create a property and map the period. this implies that the list items are named to specific month/year combinations.
  - If relative to years (which allows for a clean month header, like the list item examples above), Add a module with Time in Years and your TIMElist. Then add a line item to calculate the period based on the intersections between anaplan time in years and the TIMElist items.
    - Note, you will need to map each month in your TIME list to a numeric month value. For example, Jan=1.
    - The intersection of Jan and FY 2018, therefore, should calculate to Jan 2018... the formula will look something like Period( Date( Year(Item(Time)) , TimeList.MonthNumber, 1) )
    - The result can be used as a lookup reference from a source data module.
  - I typically avoid adding this extra layer of configuration, unless there is a strong motivation. It happens most frequently where there is a need to format things as simply as possible for executive types.

I'm a little short on time today, but let me know if you want an example, I can dig one up.

Paul

Alessio_Pagliano

Hi Paul,

That's very helpful. We would need to rename the standard Anaplan FYxx to Year1, Year2, etc.

It seems the first approach I tried was the one you mentioned on point 1 but I was struggling to get the lookups to work.

If there was an example I could look at, that would be super !

Thanks a million for your help.

Alex

PavanKumar

Hi Alex,

Steps to acheive your requirement:

1. Create a dummy time period list (List members will be 2015, 2016, 2017 etc)

2. Create a property in the list created above, say e.g i will name the property as "Anaplan Time Period". And Format that property to "Year".

3. Mannually map the Anaplan time to newly created list.

4. Use the new list created in your reporting modules. And, bring the values from modules using anaplan default time by looking to "Anaplan Time Period" property created above.

Hope this helps.

Regards,

CA Pavan Kumar

PaulRitner

Hi,

Here's a simple example showing how to aggregate Native Anaplan Time data into a False Time (reporting) module (attached).

Cheeers!

Paul

False_Time_Example_35109.docx

Alessio_Pagliano

Very interesting, I will take a better look at it tomorrow !

I might have a question you could easily help with :')

THanks!

Alessio_Pagliano

Good morning,

@PaulRitner, thanks a lot for sharing that approach. I still need to review the attachment 🙂 My first impression is that I might be able to use it in the future but I need to fully understand it and run some tests. If I understand it correctly you have re-engineered the aggregation on a false time dimension.

On the specific use case I'm working on I decided to use the time dimension because there were too many time-specific functions I wanted to make sure I could use eg cumulative, previous, next and others....

I therefore thought the easiest approach was to "plug in" reporting modules at the end and relabel the time accordingly using a list/property.

However 🙂 I've got one last specific example I'm struggling with : this time the relabelled time is on an Input module and the fake time dimension is on the "across", not on the "down" dimension....

Attached picture should give a feeling of what I've got...I was planning to create a module dimensioned by the fake year dimension and then amend the current one to lookup the value typed in by the user. However, it seems I'm failing miserably on the lookup. It seems I'm missing something obvious. Any clues or hints&tips ?

Quick Links

Can you help?

Unanswered questions

An Update on Anaplan Audit Log Reporting: A No-Code Approach
A while back, I shared a pattern for extracting and reporting on Anaplan audit data using a Python project hosted on GitHub. I wrote that during my time on the Operational Excellence Group (OEG) at Anaplan. The Python solution still works, and plenty of teams are running it today. The problem it solves hasn't changed:…
Looking for Anaplan End-Users to take a short survey!
We are looking for Anaplan end-users to provide feedback on their experiences with the Excel add-in. Interested individuals will respond to this 5-minute survey to help us understand personal needs and behavior when using the add-in. The feedback provided by survey takers is essential to the roadmap of Anaplan's products.…
Top-Down Allocations
Estimated Level of Effort:4-8 Hours of Model Building Level of Difficulty: Beginner Recommended Training: L2 Model Builder Training Persona: Casual Model Builder Potential ROI: Decreased planning time Increased accuracy of targets/spreads You Might Also Like: * Historical Snapshotting Top-Down Allocations Whether it's…