---
schema_version: "1"
id: 3d1e2fa70925452d7d63dd3674cdd476116ec21faf9bf2458a65b59e367702cc
title: Retain Original External Key Values in Package Manager
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/260-0-0/rn_mce_parent_package_manager.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_mce_parent_package_manager.htm&release=260&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 25ac346dc4c76f312a84754725d5574a5e6f1b876f719c125af55676eee1c053
description: When you deploy entities with Package Manager, the original external key value that’s specified in the originating account is retained. Journey Builder entry sources keep the event definition key value specified in the originating account. This feature makes it easier to deploy objects called by external APIs by removing the need for manual intervention.
products:
  - Cross Cloud Packages Solutions
release: "260"
---
# Retain Original External Key Values in Package Manager

When you deploy entities with Package Manager, the original external key value that’s specified in the originating account is retained. Journey Builder entry sources keep the event definition key value specified in the originating account. This feature makes it easier to deploy objects called by external APIs by removing the need for manual intervention.

**Where:** Journey Builder changes apply to Corporate and Enterprise editions, and to Professional editions with the Journey Builder add-on. Other changes apply to any Marketing Cloud Engagement edition.

**Why:** These entities are supported.

- Journey Builder Entry Source Event Definition Key
- Data Extension External Key
- Shared Data Extension External Key
- Email Triggered Send External Key
- Email User-Initiated Send External Key