SAC - Dataset changes and Impacts - a Brief

In SAP Analytics Cloud (SAC), the message "This dataset is used in the 1 dependencies listed below. Any changes to the dataset may require updates to the dependencies." refers to the fact that the dataset you're working with is being used in other SAC artifacts (such as Stories, Models, Reports, or Widgets). These dependencies rely on the structure, data, and attributes of the dataset. If you make any changes to the dataset (such as modifying fields, adding/removing columns, or changing data types), those changes might impact the dependent elements. You might need to update or adjust those dependent artifacts to reflect the changes and ensure that they function correctly.

Steps to Handle Dataset Changes and Dependencies:

1. Understand the Dependencies:

   • When SAC alerts you that the dataset has dependencies, SAC will typically list where the dataset is being used (e.g., a Story, Table, or Chart).
   • Review the list of dependencies carefully. Check how these other components (like stories or models) are utilizing the dataset, so you're aware of how changes might affect them.

2. Analyze the Potential Impact:

   • If you plan to make significant changes to the dataset (like removing or renaming fields), it's essential to analyze how these changes will impact the dependent objects.
   • For example, if the dataset feeds a table widget in a story and you remove a column, that table may display errors or missing data after the update.

3. Back Up Existing Work:

   • Before making changes, it's good practice to back up your work. You can do this by creating a copy of the existing story, dataset, or other affected artifacts.
   • This will ensure that if something breaks after the dataset modification, you have a version to revert to.

4. Make Changes to the Dataset:

   • Modify the dataset according to your needs. You may add, edit, or delete fields, or update data values within the dataset.

5. Review and Update Dependencies:

   • After making changes to the dataset, you'll need to check all the dependencies listed in SAC (like stories, charts, or widgets) to see if any of them have been affected.
   • Open each dependent object and inspect whether the changes have caused any issues. Common issues might include:
     • Missing fields in tables or charts.
     • Errors in visualizations due to removed or renamed fields.
     • Incorrect data formatting in widgets due to data type changes.

6. Update Stories or Models:

   • In dependent stories or models, update the configuration where necessary:
     • For instance, if a field was renamed in the dataset, you might need to update the corresponding field references in the table widgets, charts, or other components of the stories.
     • If a field was removed, you may need to replace it with another field or adjust the widget to handle the missing data.

7. Test After the Changes:

   • Test the dependent objects (stories, models, widgets) to ensure they are working as expected after the dataset changes. Ensure there are no missing fields, data mismatches, or broken calculations.

8. Save and Publish Changes:

   • Once all the dependencies have been reviewed and updated, save and publish the changes.
   • Confirm that the updated dataset and its dependencies function correctly in the published version.

Example Scenario:

Let's assume you have a dataset containing sales data with the fields Sales Region, Product, and Revenue. This dataset is used in a Story to display a table showing Sales by Region.

• Dependency Warning: You receive the message that the dataset is used in a Story.
• Plan Change: You plan to remove the Product field from the dataset because it's no longer relevant.
• Impact: In the dependent Story, a table widget uses the Product field in the rows. If you remove Product from the dataset, that table will display an error, and you'll need to remove or replace the Product field in the Story.
• Update: After modifying the dataset, you go to the Story, open the table widget, and either remove the Product field from the table configuration or replace it with another field like Product Category.
• Final Step: You test the Story to ensure it works properly after the dataset modification and then save your changes.

Key Terms:

SAP Analytics Cloud, SAC, Dataset, Dependencies, Story, Model, Table Widget, Fields, Update