Upsert Assets

Upserting Assets: External IDs and Names

3 Lessons

About this Course

Approximate Time to Completion: 1 hour
Instructor: Steven Woods, Solution Architect, Collibra

Course Objectives:

  • Evaluate design choices for upserts by external entity ID or by name
  • Determine whether new asset will be created or an existing asset updated when performing upserts
  • Standardize separator, case and structure prior to loading data

In this course, we will review upserts and the design choices you need to consider before you begin integration work. When integrating DGC with external applications, it’s important to evaluate whether to use the upsert with an external entity ID or by name. Both options perform the same basic function, but the difference is how DGC determines if a new asset is to be created or updating an existing asset in place.

Some important considerations when completing updates within the DGC from an external process include validating all loaded metadata assets to ensure that the name and/or external ID are unique for that domain. Governance staff should work closely with source system owners to understand the system and be involved with any upgrades in the source system prior to release. Integration developers should fully understand how system ID’s are created and managed within the source system. This is part of the criteria to adopt for successful and consistent upserts with external applications and DGC integrations.

You might be interested in these courses:

Course Materials