Can I exclude hidden objects from dependency list export?
isme
Posts: 119
My dependency tracker version is 2.7.4.1.
How do I export a dependency list for only the visible objects in the project?
The dependency export feature seems only to export a dependency list for all the objects in the project, visible or hidden.
The exported document contains a message like this:
Based on the behavior of the export function, it would appear 'visible' in this context means 'added to the project' rather than 'not hidden from view'.
Is this the intended behavior?
How to reproduce
Create an example database on your development instance using the following script:
Create a new project in SQL Dependency tracker. Add all the tables from database DependencyTracker_isme_20121113 but nothing else.
The main view of SQL Dependency Tracker looks like this:
Export a PDF dependency list.
The PDF should look like this:
The export contains all the same information as the Dependency Tracker main view. So far, so good.
Hide table g.
The main view looks like this:
Export the PDF dependency list again.
The dependency list looks exactly the same:
The table g is not visible in the Dependency Tracker main view, so I would expect to see no reference to it in the exported dependency list.
How do I export a dependency list for only the visible objects in the project?
The dependency export feature seems only to export a dependency list for all the objects in the project, visible or hidden.
The exported document contains a message like this:
This report include visible dependencies for all objects in the project.
Objects and dependencies that are not visible are not included.
Based on the behavior of the export function, it would appear 'visible' in this context means 'added to the project' rather than 'not hidden from view'.
Is this the intended behavior?
How to reproduce
Create an example database on your development instance using the following script:
CREATE DATABASE DependencyTracker_isme_20121113; GO USE DependencyTracker_isme_20121113; GO CREATE TABLE a ( b INT PRIMARY KEY, c INT ); CREATE TABLE d ( e INT PRIMARY KEY FOREIGN KEY REFERENCES a(b), f INT ); CREATE TABLE g ( h INT PRIMARY KEY FOREIGN KEY REFERENCES d(e), i INT ); GO
Create a new project in SQL Dependency tracker. Add all the tables from database DependencyTracker_isme_20121113 but nothing else.
The main view of SQL Dependency Tracker looks like this:
Export a PDF dependency list.
The PDF should look like this:
The export contains all the same information as the Dependency Tracker main view. So far, so good.
Hide table g.
The main view looks like this:
Export the PDF dependency list again.
The dependency list looks exactly the same:
The table g is not visible in the Dependency Tracker main view, so I would expect to see no reference to it in the exported dependency list.
Iain Elder, Skyscanner
Tagged:
Comments
This appears to be a known issue under the internal reference number of DT-514
Unfortunaltely I do not have an ETA for a fix.
Product Support
Red Gate Software
Sadly this is still a problem in V2.8.12.759. I have updated the Bug Report and increased the priority of this outstanding bug. I will update when a bug fix version becomes available.
Many Thanks
Eddie
Senior Product Support Engineer
Redgate Software Ltd
Email: support@red-gate.com