# Advanced Tools

## <mark style="color:$primary;">Impact Analysis</mark>

## New & Improved

### Impact Analysis Enhancements

* **“Path” Column in Impacted Objects:** A new “Path” column is now available under Impacted Objects, showing the exact location of each impacted report or object.
* **Compare Source and Impacted Objects Across Versions:** A side-by-side comparison view has been introduced to analyze Source Objects and Impacted Objects across the five most recent versions, enabling easier identification of changes over time.
* **Selection Panel Now Displays Object Types:** The selection panel now displays the object type (e.g., Report, Dataset, Page) when adding source objects, improving clarity during configuration.

## <mark style="color:$primary;">Compare Schema</mark>

## New & Improved

### Enhanced Schema Comparison with History, Scheduling, and Notifications

The Compare Schema module is enhanced to support comparison history, job scheduling, and result notifications.

* Comparison Folders can now be created to save schema pairings along with relevant metadata, enabling on-demand or scheduled comparisons.
* Each folder retains the latest comparison result, providing an at-a-glance view of schema differences and supporting actions such as re-run, delete, and impact analysis.
* This enhancement enables the tracking of schema changes over time, automates routine comparisons, and facilitates faster responses to discrepancies, thereby streamlining governance in dynamic data environments.

## <mark style="color:$primary;">Load Metadata from Files</mark>

## New & Improved

### LMDF Template Upload – Improved Validation Handling

LMDF uploads no longer rely on template file names for validation. A hidden sheet within each template now handles validation, allowing renamed templates to be uploaded successfully. Column structure validation remains active to ensure metadata accuracy and formatting integrity.

### **Masking & Restriction**&#x20;

The LMDF table column template supports masking and restriction using Yes/No options.&#x20;

* It allows assigning an existing masking policy to a column by matching the exact policy name.
* For restrictions, authorized roles can be specified to exempt them from access limitations.

## <mark style="color:$primary;">Build Auto Lineage</mark>

## New & Improved

### Rebuild Summary Lineage Option

The Build Auto Lineage module now includes a new option in the Nine Dots menu to rebuild the Summary Lineage for reporting and ETL connectors. The option supports rebuilding for either selected source codes or all source codes in the instance. It updates the simplified data flow view with the latest information for the selected source without impacting the lineage of other sources.

## <mark style="color:$primary;">Customization via System Settings</mark>

<table><thead><tr><th width="354.8333740234375">Name</th><th>Description</th></tr></thead><tbody><tr><td>buildlineage.exclude.jobtypes</td><td><p>Configure job types that need to be excluded from the Build Auto Lineage page.</p><p><strong>Parameters:</strong></p><ul><li>The default value is Empty.</li><li>Enter the job types separated by a comma(,).</li></ul><p><strong>Example:</strong></p><ul><li><strong>Single job type</strong> - View</li><li><strong>Multiple job types</strong> - View, Trigger</li></ul></td></tr><tr><td>lineage.summary.view</td><td><p>Configure the lineage.summary.view key in System Settings to control access to the Summary Lineage View across the instance.</p><p><strong>Parameters:</strong></p><ul><li>The default value is False</li><li>If set to True to enable the Summary Lineage toggle in the Lineage screen</li><li>If set to False to hide the toggle</li></ul><p><strong>Notes:</strong></p><ul><li>Only System Administrators can modify this key</li><li>A complete lineage rebuild is required after enabling or migrating this setting to ensure data accuracy</li></ul></td></tr></tbody></table>

## <mark style="color:$primary;">Advanced Jobs</mark>

| Name                                                                                            | Description                                                                                                                                                                                                 |
| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Curated report column info that maps to the appropriate reporting object based on the connector | This job enables the movement of curated column-level metadata from higher-level reporting objects to their associated downstream entities, supporting consistent metadata alignment across all connectors. |
| S3 to Snowflake Lineage using DDL Commands                                                      | This job creates a lineage from S3 to Snowflake.                                                                                                                                                            |
| Build Lineage from Excel File                                                                   | This job builds the lineage from an Excel file.                                                                                                                                                             |
| Lineage using YML Files                                                                         | This job creates the lineage using the YML files.                                                                                                                                                           |
| HDFS to HIVE Lineage                                                                            | This job establishes lineage from HDFS to Hive based on the location of Hive external tables, as specified in the custom fields of the Hive table.                                                          |
| FME TO CARTO VISTA Lineage                                                                      | This job establishes lineage from FME to Carto Vista based on the FME components.                                                                                                                           |

***

Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.