---
schema_version: "1"
id: 2bd696f8786568ffc723ea9be8e33171648156e608727c14bdf17cea96c8014a
title: Creating Custom Matching Keys (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_build_tool_create_custom_matching_keys.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_build_tool_create_custom_matching_keys.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7a219b1f0967773377d7f7567b463a799b3aa07a99f7dd235bf35aaa8e74f1f7
description: For the managed package runtime, Vlocity Matching Keys are a custom metadata type in Salesforce. Vlocity matching keys contain seven fields
products:
  - Omnistudio
release: "264"
---
# Creating Custom Matching Keys (Managed Package)

For the managed package runtime, Vlocity Matching Keys are a custom metadata type in Salesforce. Vlocity matching keys contain seven fields

![Managed Package app icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/resources-global/_corporate/images/managedpackageicon.png) This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see [Omnistudio Help](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_standard.htm&language=en_US).

Create these keys if you want to support connections between SObject Id fields that are not already supported by data packs, or if you would like to change the Vlocity Default for any SObject. Matching Keys created outside the Managed Package always override those contained inside (Post Vlocity v15).

For Custom Settings MatchingKeyFields\_\_c should always be Name.

This feature changes the matching key of Product2 to its ProductCode instead of using Vlocity's GlobalKey field. This feature is useful if your project has unique product codes for each Product2. As long as the same matching keys are used in each org, there are no issues with using custom matching keys. Because these are Salesforce metadata, they can be added to the version controlled project as well.

  
| Name | API Name | Description |
| --- | --- | --- |
| Matching Key Fields | MatchingKeyFields\_\_c | Comma-Separated list of Field API Names that define Uniqueness |
| Vlocity Matching Key Name | Name | Name of the Matching Key |
| Label | Label | Label of the Matching Key |
| Object API Name | ObjectAPIName\_\_c | Full API Name of the SObject |
| Matching Key Object | MatchingKeyObject\_\_c | Full API Name of the SObject |
| Return Key Field | ReturnKeyField\_\_c | Always "Id" for data packs |
| Composite Unique Field | CompositeUniqueFieldName\_\_c | Leave empty - Reserved for future use |
|   |   |   |