---
schema_version: "1"
id: 4dda2dd7307a2cf7a7737b025ac77de3d03244c29be656660e0da4bd22b4d73e
title: Versioning Best Practices (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_versioning_best_practices.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_versioning_best_practices.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: d27555d58e6b33c55aea25a752d9bd9a031f71925995ec3b5b1ef441aa19e2a9
description: For the managed package runtime, consider the following best practices for versioning in Omnistudio.
products:
  - Omnistudio
release: "264"
---
# Versioning Best Practices (Managed Package)

For the managed package runtime, consider the following best practices for versioning in Omnistudio.

![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).

- When working with Omnistudio-authored components in a client org:
    
    - Set a unique name for the new component if you are only using the original component as a template to start from.
    - Set a unique author for the new component when replacing a Vlocity component with your own inside of a larger app. For example, inside of CPQ you can replace one component without having to overwrite and clone the whole app.
- When you import data packs, components of the same type are matched by Name, Author, and Version combination. If this combination is not unique, a warning is displayed that there is a pending overwrite. Importing components doesn't create new versions of them.
- Make sure to activate your components before creating a data pack. When you export data packs, only active components are exported.
- Use source control. This versioning workflow is not as fail-safe as the security that source control provides.
- To work efficiently, use IDX Workbench, or, for large or complex deployments, use the Omnistudio Build Tool, which is available from [GitHub](https://github.com/vlocityinc/vlocity_build). The Build Tool is a command-line tool that packages related objects together as data packs, ensuring that dependencies are preserved.