Planning on Public Versions

In SAP Analytics Cloud, you can edit public versions directly if you have the required permissions. Editing a public version creates a temporary private version that only you can see until the changes are published.

Context

When you make edits to a public version, the version is put into Edit Mode. This creates a private version of the public version that only you can see until the changes are published.

You can leave edits unpublished to resume later, however, it is best to publish changes often when editing public versions. If other users are editing the same version, your changes could overwrite theirs when you publish because the most recent update will overwrite previous states.

If you make changes to a version that conflict with another user's changes published to the same version while you were editing, you can choose whether to publish only your non-conflicting changes and discard your conflicting changes, or publish all your changes while overwriting the other user's changes.

Note

The choice of whether to discard or overwrite conflicting changes is only available to models with measures. It is not supported for classic account models.

Note

To have such a choice, go to Start of the navigation pathSystem Next navigation step Administration Next navigation step System ConfigurationEnd of the navigation path, and turn on the toggle of Display options to resolve version publish conflicts.

You can also use Version Management APIs to publish, delete or revert data from planning versions even if the table is not planning-enabled. For more information, see Use Version Management APIs on SAP Analytics Cloud Data Models

Using the Recommended Planning Area

When you put a public version into Edit Mode, you define the planning area for that version. The planning area corresponds to a versions' data that is used for all planning actions, for example, entering values or running data actions. If the model has a recommended planning area defined, the recommended planning area will be put into Edit Mode to optimize performance when working with large versions. The scope of the recommended planning area is configured in the model settings, and defines a slice of data that you can plan on based on data access control, data locking, or both. For more details about the planning area, see Optimize Planning Models Using the Planning Area

If your model has a recommended planning area applied, you can still choose to put all version data into Edit Mode by manually selecting Start Edit Mode on a public version in a table or the Version Management panel. However, write permissions still apply and you will only be able to publish changes within your write permissions.

You can also choose to Customize Planning Area when putting the public version into edit mode. This option will let you choose which data will be put into edit mode. However, you will only be able to publish changes within your write permissions.

Note

Data actions will only run on data within a public versions' planning area when the version is in Edit Mode. If you use the recommended planning area, data actions will only run on this data. If you put all version data into Edit Mode, data actions may run on all version data, however, write permissions will still apply.

Procedure

  1. Make your edits to a public version in a table.

    If a recommended planning area has been defined on the model, this data will be put into Edit Mode once the first changes are made.

    • If you want to manually decide which data to put into Edit Mode, do one of the following:

      • Choose your public version in the Version Management panel and select Start of the navigation path Next navigation step Start Edit ModeEnd of the navigation path.

      • Right-click the version name in a table and select Start of the navigation pathVersion Next navigation step Start Edit ModeEnd of the navigation path.

      If your model has a recommended planning area defined, you can choose from the following options:

      • Recommended Planning Area: Only a recommended subset of data will be put into Edit Mode, which can help optimize performance on large versions.

      • Customize Planning Area: Choose the data that will be put into Edit Mode.

      • All Version Data: All data in the version will be put into Edit Mode.

  2. After you have finished your edits, do one of the following actions:
    Option Action

    Publish all the public versions that you are editing.

    		 Choose one of the following options:
    • Select Publish Data from the toolbar.

      • In the Publish Data window, you'll have a chance to check which versions are involved.

    • Navigate to another part of the application, then select Publish and Leave.

      • You can select Show Details to check which versions are involved

    Publish one public version.

    1. Select a table with the public version you want to publish.

    2. Select Version Management from the toolbar.

    3. Select Publish for the version you want to publish.

    4. Select which version you want to publish your changes to, then select Publish.

    Revert changes for one public version.

    1. Select a table with the public version you want to publish.

    2. Select Version Management from the toolbar.

    3. Select Start of the navigation path More Next navigation step  RevertEnd of the navigation path for the version you want to revert, then select OK.

    Publish or revert changes to multiple versions.
    1. Select Start of the navigation pathPublish Data Next navigation step  AdvancedEnd of the navigation path from the toolbar. A dialog appears, prompting you to revert your changes or publish them. Choose one of the following options:

      • Next to each version, select either Revert or Publish.

      • To update all the versions at once, select either Revert All or Publish All.

    2. Select OK.

    Some data actions will publish changes to a target version automatically. In this case, all unpublished changes to the public version will be published.

Related Information