Tutorial: How to replace a dependency

objective the objective of this tutorial is to help you use {{product name}} grid to visually analyze {{scenario singular lowercase}} dependencies and plan updates in this tutorial, you will use {{product name}} grid to plan to migrate away from an existing google sheets spreadsheet and use another data element, for example, an airtable base with the help of {{product name}} grid, you can plan changes effectively and ensure a smooth, error free transition without disrupting existing workflows requirements before using {{product name}} grid, ensure that you have an existing {{scenario singular lowercase}} with dependencies step 1 open your scenario log in to {{product name}} com in the left sidebar, navigate to scenarios from all scenarios , click the {{scenario singular lowercase}} that you want to update in this example, you plan to replace the google sheets spreadsheet with an airtable base step 2 open make grid to analyze the scenario and its dependencies in the {{scenario singular lowercase}} diagram, click the grid button once {{product name}} grid opens, you can view the {{scenario singular lowercase}} and its dependencies in the right side panel, you can view the details of the {{scenario singular lowercase}} click on a specific dependency you want to make changes to, such as the google sheets spreadsheet in this example {{product name}} grid highlights the {{scenario singular lowercase}} dependencies click links to view the {{scenario plural lowercase}} that depend on the selected dependency in this example, you can view which {{scenario plural lowercase}} read or write to the google sheets spreadsheet click attributes to view where specific attributes of the selected dependency are used in example, you can view which google sheets columns are referenced in which {{scenario plural lowercase}} click raw data to see the json data for the dependency, which is useful for advanced debugging and understanding the data structure {{product name}} grid offers a comprehensive visual representation of how a dependency is interconnected within a {{scenario singular lowercase}} and with other {{scenario plural lowercase}} this holistic overview allows you to trace data flows, understand dependencies, and plan changes effectively, minimizing the risk of breaking existing logic or workflow step 3 plan the replacement identify the new replacement, an airtable upsert a record module, for example before making any changes, use the information from the attributes and links view to create a clear plan to map the old data attributes to the new dependency this ensures data integrity add the new airtable base to your {{scenario singular lowercase}} reconfigure existing dependencies to read and write to the new replacement by thoroughly analyzing your {{scenario singular lowercase}} and workflow with {{product name}} grid, you should be able to complete the transition smoothly