All ideas are welcome. Just because the Idea doesn't make it into the product immediately does not make it a bad idea.
Document the relationship between Source tables and Target Tables to enable automation, load dependencies, etc.
If we have the constraints from the scanners (Foreign Keys, Check Tables, Text Tables, etc) it should be possible to derive these relationships automatically. If not, enable a user to manually define these relationships.
Once we know the relationships between Tables and Datasets, we can potentially:
Support automation when mapping from secondary tables.
Determine the default LOAD Order - which cascades into Validation Hub, PMO Dashboard, Execution Hub, etc.
Automate more complex readiness reports between objects, extensions, etc.
Present better Visualizations of the Project Plans, Mock readiness, Load Progress, etc.
John Munkberg
