Table Inserts and Object Dependencies

  • 8 March 2023
  • 2 replies

I have a table with a table Insert from a view (actually multiple views) underneath it. The problem is that this table sometimes is empty because the Data Lineage is wrong. It seems that we need to have Object Dependencies for Table Inserts. 
2 Questions about that: 

  1. When creating a "Table Insert" get a message that "Object Dependencies" are required?

  2. Is it enough to check the next child view (in my case) in the "Object Dependencies" if you have one table insert? Or should it be the first child table? Or should all underlying views/tables be included?


Best answer by Thomas Lind 8 March 2023, 14:38

View original

2 replies

Userlevel 6
Badge +5

Hi Patrick

I would set the object dependencies on the tables that the views use.

For reference I have a custom table insert that uses a stored procedure and two tables.

If I were basing my table insert on a view, I would still set the object dependencies to the tables the view used.

Besides that I always map my views, so the linage works through them.


Userlevel 6
Badge +5

Hi @p.ruijter is your issue resolved? If so can you please help us by marking the best answer?