For the managed package runtime, when developing on a large project, exporting data packs through queries isn't an ideal process. We recommend that you use a manifest-driven workflow to track the major items that you’re working on. Then, extract those items to commit to version control. The manifest section of the job file can be used to create a collection of data packs to be exported or deployed. Manifests are based on the data pack key of each data pack.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
- Data Pack Key (Managed Package)
For the managed package runtime, each data pack has a data pack key that represents its unique name in the data pack system. After a data pack is exported, the data pack key matches the folder name of the data pack. - Using the Data Pack Key in the Manifest (Managed Package)
For the managed package runtime, add the data pack key to the manifest of the job file to drive export of this product along with all its dependencies. - Creating Job Files for the Omnistudio Build Tool (Managed Package)
For the managed package runtime, when you define your project through a manifest, we recommend that you create two job files: one for export and one for deployment. - Other Job File Settings (Managed Package)
For the managed package runtime, the job file has a number of additional runtime settings that you can use to define your project and to run exports and deployments run. Modify the default settings only to account for unique issues in your org.