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
  • Data Integration
  • All Products

Table of Contents

Search

  1. Preface
  2. Project and asset management
  3. Source control
  4. Asset migration
  5. Bundles

Asset Management

Asset Management

Back Next

Source control pulls

Source control pulls

Pull an object to add it to the organization or replace the version of the object in the organization with the version in the source control repository. You can pull a project, folder, or an individual object that isn't checked out by another user.
Before a pull takes place, you can review the potential results of the pull. You can cancel the action or select objects to exclude from the pull.
The following image shows a preview page with potential results in the
Status
 column:
The preview page shows that a folder and several assets will be included in the pull. The status for the folder is "Reuse existing object." When a folder with the same name already exists, it is reused. The status for the assets is "Overwrite existing object." When an asset already exists in the organization, the pull will overwrite it using the Git version that you select.
You can also test the pull to see if any errors might occur. If any errors appear, you can exclude the objects from the pull or close the page to cancel the pull.
A pull doesn't include dependent objects. For example, in
Data Integration
, if you pull a mapping that uses a saved query, the pull doesn't include the saved query.
A pull doesn't change the state of pulled objects in the organization. For example, if an object was checked out before the pull, it remains checked out after the pull.
Consider the following rules and guidelines:
  • If you want to pull an object that uses a connection or runtime environment, be sure that the organization includes a connection and runtime environment before you perform the pull. When you select an object that uses a connection or runtime environment, you can select a runtime environment and connection to use on the test page.
  • Informatica Intelligent Cloud Services
     doesn't consider capitalization in object names. As a result, you can't pull a project that contains multiple assets that have the same name with different capitalization. For example, if you try to pull a project that contains an asset named "sales" and an asset named "SALES", you receive an error because a project or folder can't contain multiple assets with the same name.
  • You can pull objects regardless of whether your organization can or cannot update the source control repository.
0 COMMENTS
We’d like to hear from you!