Table Relationships

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:

  1. Support automation when mapping from secondary tables.
  2. Determine the default LOAD Order - which cascades into Validation Hub, PMO Dashboard, Execution Hub, etc.
  3. Automate more complex readiness reports between objects, extensions, etc.
  4. Present better Visualizations of the Project Plans, Mock readiness, Load Progress, etc.

Please authenticate to join the conversation.

Upvoters
Status

Planned

Board

Syniti Knowledge Platform

Tags

Migrate

Date

Almost 3 years ago

Author

Subscribe to post

Get notified by email when there are changes.