See the impact of Marking changes

You can use Data Lineage to evaluate how changes to dataset Markings can impact derived datasets. This can be useful when removing Markings.

Access simulation mode

1. Open the Access information side panel.
2. Toggle on Simulate access requirements.
3. Select any dataset on the graph.
4. Click Edit markings.

Simulate Marking changes

To simulate Marking application, search for the Marking you want to apply, check the box next to the Marking, and then select the Simulate changes button.

Markings that are already applied on a dataset will appear as selected. To simulate Marking removal, uncheck the box next to the Marking and click Simulate changes.

Analyze the simulated graph

When in simulation mode, the graph coloring will indicate the datasets affected by the Marking changes. The graph colors are labeled in the interface and can represent the following dataset statuses:

• Simulate changes applied appears on the datasets to which you applied changes.
• Access affected appears on datasets for which the Markings before and after the change will be different.
• Access unaffected appears on datasets for which the Markings before and after the change will remain the same.
• No visible transactions appears on datasets that have not been built yet, or where you do not have permission to see transactions.

By selecting any of the datasets, the Access information side panel will show the simulated access requirements. You can toggle simulation mode on and off to view differences without losing any of the simulation changes.

Tips for understanding changes

Before making changes, we suggest consulting the Markings documentation to learn more about the impact of Markings on users.

When simulating Markings, consider the following:

• Datasets can stop propagating Markings via code.
  
  • In the Permissions coloring, nodes on the Data Lineage graph that stop propagating Markings show that data access was modified via code. This message will also appear in the Access information section of the node properties side panel.
  • In the Code Helper, you can check the code for a dataset to see if it stops propagating Markings by using the term stop_propagating.
• Datasets can have Markings propagated to them from other inputs; expand the dataset inputs by clicking on the left arrow in the dataset node.
• Markings can be applied on the parent Project or folder; Markings will have a folder icon on their left when simulation mode is not enabled, and will show a folder icon in the Marking simulation menu when simulation mode is enabled.