Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Informatica Data Quality 10.4.0
  • All Products

Table of Contents

Search

  1. Preface
  2. Informatica Developer
  3. The Model Repository
  4. Searches in Informatica Developer
  5. Connections
  6. Physical Data Objects
  7. Flat File Data Objects
  8. Logical View of Data
  9. Viewing Data
  10. Application Deployment
  11. Application Patch Deployment
  12. Application Patch Deployment Example
  13. Continuous Integration and Continuous Delivery (CI/CD)
  14. Object Import and Export
  15. Appendix A: Data Type Reference
  16. Appendix B: Keyboard Shortcuts
  17. Appendix C: Connection Properties

Developer Tool Guide

Developer Tool Guide

Back Next

Inheriting Direct and Indirect Dependencies

Inheriting Direct and Indirect Dependencies

Choose to inherit direct and indirect dependencies when you edit an application object that is used by many other application objects in order to propagate the changes to the parent objects.

Example

You have an application that contains multiple mappings that use the same relational data object. Each mapping ultimately transforms the data in the data object for a different purpose. To schedule mapping runs, you deploy the application to the Data Integration Service.
Later, you use the Developer tool to synchronize the relational data object with the relational database. To propagate the synchronized data to the mappings in the run-time application, you create a patch that inherits direct and indirect dependencies:
When you create the patch, you select one of the mappings that uses the data object and the patch inherits every other mapping that uses the data object. The following image shows how the inheritance appears in the Incremental Deployment Wizard:
This image shows the Source Object Selection page in the Incremental Deployment wizard. Next to Include, the option "Selected objects and first-degree related objects" is selected. The table lists the following objects: the mappings Mapping A, Mapping B, and Mapping C; and a data object. The data object is selected. The three mappings are inherited, and their rows are greyed out. The bottom of the page states that 4 out of 4 objects are selected, 4 out of 4 objects will be updated, and 0 objects will be added.
The following image indicates the selected object and the inherited indirect dependencies:
This image shows a dependency diagram for an application. In the application, the mappings Mapping A, Mapping B, and Mapping C use a data object. The mapping Mapping A has the label “selected.” The data object has the label "direct." The mappings Mapping B and Mapping C have the label “indirect.”
0 COMMENTS
We’d like to hear from you!