Switchover and FY year settings

Monpero

Is there a workaround on:

1 Updating Switchover period from the NUX App

2 Is there a workaround on updating the Current Fiscal Year of the Time Settings from the NUX.

Please your reply will be really helpful.

Accepted answers

AjayM

Hi @innocent ,

Workaround to update switchover period - yes, I tried and shared below, hope this helps.
Workaround to update current fiscal year - unfortunately, no

Update Switchover Period:

Assuming my current switchover month is Sep 20:

I created a SYS module to identify current and next switchover month:

Please note that my 'Switchover Period' lineitem's formula scope is only 'Current Version'

I created another module 'Import Switchover', which I published on UX page, and also used it to update switchover month through an action. Please note that the formula scope for both these lineitems is 'Current Version' only

From Versions tab/list, create an import action to import 'Next Switchover Month' from 'Import Switchover' module.

Note: I recommend careful consideration of user access to this import action. You might not want every enduser to be able to update switchover period, considering the importance and implications of changing it.

Finally, publish the 'Import Switchover' module and action on UX page

Cheers!

All comments

AjayM

Hi @innocent ,

Workaround to update switchover period - yes, I tried and shared below, hope this helps.
Workaround to update current fiscal year - unfortunately, no

Update Switchover Period:

Assuming my current switchover month is Sep 20:

I created a SYS module to identify current and next switchover month:

Please note that my 'Switchover Period' lineitem's formula scope is only 'Current Version'

From Versions tab/list, create an import action to import 'Next Switchover Month' from 'Import Switchover' module.

Finally, publish the 'Import Switchover' module and action on UX page

Cheers!

Monpero

Thank you very much this is really helpful also clear and precise 🙂.

Monpero

Hi a quick question just for clarity, when I have multiple versions like this one above, do I set the formula scope to current version for all the different versions even when I have the 2021 12 0v2 ticked as the current version like the example below

AjayM

Formula scope is a setting that is set to 'current version' for the lineitems in the module, because you don't want to apply switchover to any other version, but just for the current version (in your example, it is 2021 12 0v2, for which the switchover has to be updated)

So whenever you change your current version in "Versions" list, this formula scope setting will take care to apply updated switchover only to that current version, but not to the other versions.

Monpero

Thank you very much @AjayM this is very helpful.

Quick Links

Can you help?

Unanswered questions

New UX Filtering for Hierarchy sibling
I have A6 as the parent list and two sibling lists: A6.5 and A7. The A7 list includes an attribute that maps to A6.5. In the UX, the user will select A6.5 using a content selector, and the grid (dimensioned by A7) should display only the A7 items associated with that selected A6.5. Since the selector is a page context and…
A reminder of Bulk Copy - Current year to Prior year version for YoY analysis
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…
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.…