Define Dependent Objects

[DaveStabilify]

Adding context menu options to generate a query to display dependencies for the selected object from the metadata pane.

[dgosbell]

This looks good. There are probably a couple of small tweaks we need to make.

Both the TreeViewTable and TreeViewColumn classes implement the IADOTabularObject interface. I've started working on exposing a Name and ObjectType property through this interface. We would need to swap over to using Name instead of Caption as the Caption property can change if the model has translations, while the Name is the how the object is referred to internally.

I'd also like to look at maybe altering the WHERE clause to filter on REFERENCED_TABLE for tables and REFERENCED_OBJECT for columns/measures.

Finally I think I can possibly extend the SendTextToEditor event so that it can also trigger the execution of this query, which would be a nice enhancement.

[DaveStabilify]

This looks good. There are probably a couple of small tweaks we need to make.

Both the TreeViewTable and TreeViewColumn classes implement the IADOTabularObject interface. I've started working on exposing a Name and ObjectType property through this interface. We would need to swap over to using Name instead of Caption as the Caption property can change if the model has translations, while the Name is the how the object is referred to internally.

I'd also like to look at maybe altering the WHERE clause to filter on REFERENCED_TABLE for tables and REFERENCED_OBJECT for columns/measures.

Finally I think I can possibly extend the SendTextToEditor event so that it can also trigger the execution of this query, which would be a nice enhancement.

Sounds good. I wasn't too concerned about triggering the execution of the query because the other context menu options don't behave that way but it's up to you. Also, I just pushed a minor fix to the MetadataPaneViewModel class.

[dgosbell]

Yes, the query execution is just a "nice to have", but we don't currently have any other features that generate a fully executable query. The current features all inject definitions into existing queries and the expectation is that often the user may want to do some performance tuning on these definitions before running them.

[DaveStabilify]

That's a good point.