Review these considerations before you set up and run bulk or dynamic bulk copy actions.

Exercise caution when you perform bulk copy actions with numbered lists and display names. Line items that contain display names are copied as part of the bulk copy. As a result, the display name repeats for both list members. This impacts bulk copy and dynamic bulk copy actions.

From an action card on a page, to run a dynamic bulk copy action with selective access enabled for that list, workspace administrators must have:

  • List members or a parent list added to their user profile.
  • Read or write access to the list members or parent list. 

You can only choose ‌list members (that are included in your selective access) as a source or target, regardless of their read-or-write status. If a list member is read-only, you can still pick it as a target. The read/write status doesn't determine what can be a source or a target.

When you run a dynamic bulk copy action in the Actions section of the modeling experience, selective access has no impact. 

Bulk copies and dynamic bulk copies against time can cause‌ destructive changes as they apply equally to all versions:

  • Bulk copies for time apply against actual versions, and periods before current or switchover periods.
  • When you perform a bulk copy from a period in the future to a period earlier than the switchover period, this results in actuals from the future period applied to the target period.  
  • Bulk copies from historical periods to a future period result in populating or overwriting actuals to an incorrect period.

Bulk and dynamic bulk copy actions don't factor in read-only access drivers applied with dynamic cell access. Cells that have read access are included in the bulk copy. These cells get overwritten. 

If you copy between list members with different Boolean selections with dynamic cell access read-only or write-only behavior, the target inherits the Boolean from the source member. 

Additionally, the target list member inherits the selections from the source list member for Booleans drivers. Examples of Boolean drivers include modeling logic, record workflow approvals, and overrides. 

Bulk and dynamic bulk copy actions ignore user access settings, except for model role access to the action.

If you select the Enable all users with access to the action to run it checkbox when you set up a bulk copy action, this access exception applies to any user with access to the action.

If a nonworkspace administrator runs a process with bulk copy or dynamic bulk copy actions, the process might succeed or fail based on the action settings.

To successfully run a process with a bulk copy action:

  • Workspace administrators must select the Enable all users with access to the action to run it checkbox when they set the bulk copy action.
  • The process can't include dynamic bulk copy actions.

The process fails to run under these conditions:

  • When the bulk copy action isn't enabled for all users during the action setup.
  • When the process includes only dynamic copy actions.
  • When the process includes both a bulk copy and a dynamic bulk copy action.

The process fails to run if it includes both a bulk copy and a dynamic bulk copy action. Yet, a bulk copy action in the process might successfully run if both of these conditions are met:

  • The bulk copy action must be enabled for all users during the action setup.
  • The bulk copy action must be added before the dynamic bulk copy action in the process. The dynamic bulk copy action will still fail.

Be aware that your model history only reflects that a data change has occurred, who triggered it, and the time stamp. The history doesn't show which action was triggered, what dimension was updated, or the specific data points updated.  

Cell history won't show any change.