Skip to main content
rakesh_rana
Member
Oct 8, 2026 9:31 AM UTC
Solved

Copying formulas on mass to different periods in account dimension

Dear all I have written some formulas to accounts which vary by scenario and time however want to be able to copy these formulas to different time periods on mass - without having to go into each formula constricted by time period and copying across to a different OS application (dev to prod e.g.) - using the copy paste format.

Is there an optimum recommendations that I can get around this?
 

RobbSalzmann
RobbSalzmannAnswer
Employee - Advisor
Oct 9, 2026 9:49 PM UTC

Is there an optimum recommendations that I can get around this?

One option is to move the time and scenario into the formula itself, so there’s nothing to copy year to year. api.Time.GetYearFromId(api.Pov.Time.MemberId) gives the year and api.Scenario.GetScenarioType() gives the scenario type, and the formula branches on those. Enter it once at Default Scenario Type and Default Time and remove the period entries.

If what changes each year is a number rather than the logic, I’d put that in a driver account entered by period and leave the formula alone.

View in thread

2 replies

Haritha_Dev
Member
Oct 9, 2026 7:24 AM UTC

Hi,

You can do this with an XML extract and load:

  1. Go to Application > Tools > Load/Extract and extract the Account dimension to XML.
  2. In the file, each formula is a <property name="Formula" scenarioType="..." time="..." value="..."> element. Duplicate the element for the new period and change only the time= (and scenarioType= if needed) attribute or find and replace on the attribute text (for example time="2024" to time="2025") rather than on the bare year, so formula code isn’t touched.
  3. Load the edited XML into the target application (dev or prod)

Note: Try it first with 2 or 3 accounts

Thanks!
Haritha

RobbSalzmann
Employee - Advisor
RobbSalzmannEmployee - AdvisorAnswer
Employee - Advisor
Oct 9, 2026 9:49 PM UTC

Is there an optimum recommendations that I can get around this?

One option is to move the time and scenario into the formula itself, so there’s nothing to copy year to year. api.Time.GetYearFromId(api.Pov.Time.MemberId) gives the year and api.Scenario.GetScenarioType() gives the scenario type, and the formula branches on those. Enter it once at Default Scenario Type and Default Time and remove the period entries.

If what changes each year is a number rather than the logic, I’d put that in a driver account entered by period and leave the formula alone.

    Terms & ConditionsAccessibility statement