Lineage Visual diagram

Lineage and Visualization

  • 7 February 2023
  • 5 replies
  • 619 views

Userlevel 3
Badge +3

As your setup grows, the increasing complexity can make it hard to keep track of all objects and their dependencies. To help you with this, TimeXtender offers these visualization features: Data lineage and Relation Diagram. The relation diagram is only available on tables, while Data lineage is available for fields and measures in a data warehouse or semantic model instance.

The purpose of data lineage is to show you where the object in question gets its data from. The relation diagram shows you the relations to and from the table in question.

Note:  It is recommended to save all changes in the instance before generating data lineage.

Showing Data Lineage or Relation Diagrams

To show data lineage, right click on a field, click Data Lineage:

  • Under Content section (on top-left) check boxes for objects to show, then click the refresh button to show the lineage. 

     

Customizing the Display

In the visualization window, you have different options to customize the display:

  • Click an object to have the connections to and from the object highlighted.
  • Click and hold on an object to move it around and release the mouse button to place it.
  • Click the arrow in the header of an object to hide or show object details.
  • Right-click the background in the window to bring up a menu with different options for organizing and displaying the data:
    • Click Reset Layout to make TimeXtender reset the layout.
    • Click Collapse All or Expand All to either collapse the objects to create a better overview, or expand the objects to see more details.
    • Click Zoom InZoom Out or Zoom 100% change the size of objects.

5 replies

Userlevel 3
Badge +1

Is this feature related to “Object Dependencies” menu option:

 

 

For what this option is used?

Userlevel 3
Badge +3

You may configure dependencies on the table (right-click table > Advanced > Object Dependencies). Select the tables that should be executed prior to the selected table. This may help avoid a deadlock

Hi 

Do the tables in question need to be deployed afterwards?

And another thing: 

Are dependencies respected in multi-threaded execution packages?

Userlevel 3
Badge +1

Hi,

It seems that the data lineage view show incorrect schema for the tables. It says that the scehma is [dbo] for all tables, even if they have different schemas. This is even the case in the screenshots in this post.

It would also be nice if you would bring back the feature to double click on a node to go to that object in the GUI. This is incredibly valuable when working in large solutions.  

Reply