Using Data Actions to Copy Data Within a Model

Copy actions allow you to copy data from one set of members to another, specifying options for filters and aggregation. For example, you can copy data for a product in one region to another product in other regions.

In the following example, the data action is set up to copy data by version and year at the same time. For example, copy the 2023 actual data to the 2024 plan data.

The copy rule doesn't allow the use of version, so there are two key points to remember:

1. Use a parameter for the source version. The source version parameter is then added to the context which will result in a prompt.
2. Every data action will always prompt for the target version regardless of whether the target version prompt is in the filter or not.

Every data action has a system-provided Filter for Version. The default version filter is the target version prompt.

• When choosing members for the copy action settings, you can use a parameter instead of dimension members to make your data action more flexible. Parameters can make it easier to update your data action, and they prompt you for values while running the data action.
• When you define a copy action, the source distribution aggregation will also be copied. You can override this functionality by specifying any dimensions that need to aggregate data differently than the source.
• When a copy action is executed, the default action is to Overwrite the data. When defining the copy action, you have the option to change to Append (add) the data to existing values for the target members.
• Depending on the Filter and Aggregate To settings, you may not need to add a copy rule:
  • If you want to copy the 2025 Forecast to a target version, then you only need to filter the step to the Forecast version and 2025.
  • If you want to copy the 2025 Forecast to 2025 and 2026 in the target version, then a copy rule is required.

In the Aggregate To area of a data action, add any dimension where you want to override the default disaggregation behavior.

For dimensions that aren't included in the Aggregate To area, the copied data will match the distribution of the source data by default. This behavior is similar to copying and pasting a cell with the Paste Details option enabled.

For example, if you want to remove the distribution of data to different customers for privacy reasons, you can aggregate the data to the Unassigned member of the Customer dimension. In this case, all of the copied data is booked to the Unassigned member.

To copy data from one year to another and at the same time copy actual to plan:

• The version filter must be set to the source version, for example, actual or a parameter for the user.
• The copy rule would then contain the source and target time values or parameters.

When Data Action Triggers are added to stories, they appear as push buttons and can be configured using the right panel.

The prompts are based on the data action parameters. In a story, these are the input options:

• Prompt
• Fixed Value

If you choose the Prompt type, there are four Value options:

1. Member Selection
2. Default Value (based on the default value set in the data action configuration)
3. Story Filter
4. Input Control

When a data action is run by selecting the push button in the story, a prompts dialog allows for dynamic member selection.

If the data action is set to always run in the background, or if you select Run in Background  after starting it, you'll return to your story or extended story. You can keep working with your story or extended story but you'll have to wait until the data action finishes to make changes to the same version and you may need to refresh to see the results.

A message appears when it’s complete or you can check the  Notifications list for the results.

Data actions can be set up in stories to publish automatically, so that planners don't have to publish data in a separate step. Alternatively, if a data action is set up in a story not to publish automatically, then the data can be reverted.

There are three publishing options:

1. Do not publish.
2. Publish and fail if there are warnings.
3. Publish and ignore warnings.

   If there is an issue with some records but not all, this option will process the good records.