The Element Details tab of the Data Set Editor provides many options that allow you fine-grained control of record deployment for each data set element in the data set.
To set object properties:
- From the Data Set Editor, in Tabs view, click the Element Details tab.
- Select the options described below that you desire to enable.
- Click Save.
By default this box is checked for the deployment object and every selected object in the data set. When selected on the root element, the data set is available for deployment. When deselected on the root element, the entire data set becomes inactive. If unchecked on an individual parent/child objects, AppOps Release will skip deploying that object and all of its incoming and outgoing relationships.
Settings That Affect Every Object in the Data Set
- Create Missing Fields – If checked, AppOps Release will create any fields that do not exist in the destination environment during the deployment and grant access to the newly-created fields to the username that authenticated the destination environment. If unchecked, AppOps Release will only deploy fields that already exist in the destination environment.
- Sync Picklist Field Values – When checked, AppOps Release will add/remove picklist values to/from the destination environment as needed to ensure the values for all picklists fields in the data set match the source environment’s values. To only sync values for specific picklist fields, use Field Properties on the Object Fields tab. The Standard Picklist Support topic contains a list of the picklists AppOps Release can synchronize during data deployment.
- Set Audit Fields – When checked, AppOps Release will deploy the records with the audit field values from the source record. When left unchecked, the records will reflect the date and time of the deployment and the username that was used to authenticate the destination environment.
- Ignore Namespace – When checked, AppOps Release will match objects and fields to the API name, even if the namespace is different from the source to the destination. If unchecked, AppOps Release will only make a match if the namespace and API name are both the same.
|Create Missing Fields and Sync Picklist Values are legacy features. We recommend using AppOps Release’s metadata deployment capabilities to deploy new fields or update picklists.|
Settings That Only Affect a Single Object
- Skip Updates – When checked, AppOps Release will not deploy records that already exist in the destination environment, regardless of whether or not the data matches.
|When using Virtual External ID as your record matching method, AppOps Release also skips reinserting any records you deleted from the destination org that you had previously deployed using VEID, and, any records with IDs that match in the source and destination orgs (likely created through a sandbox refresh) that you have not previously deployed using VEID do get updated. For assistance working around these known limitations, email firstname.lastname@example.org.|
- Skip Inserts – When checked, AppOps Release will only deploy records that already exist in the destination environment.
- Replicate Owner – When checked, AppOps Release maintains the record owner from the source environment. When unchecked, AppOps Release assigns the record to the username that was used to authenticate the destination environment.
- Replicate Record Type – When checked, AppOps Release maintains the record type from the source environment. When unchecked, AppOps Release uses the default record type of the user who authenticated the destination environment.
- Ignore Relationship Constraint – When selected, AppOps Release copies all source org records of this object type to the destination org. When deselected, AppOps Release copies only records related to parent or child records AppOps Release is deploying. AppOps Release applies query filters in either case. Refer to the related data deployment concept for more information.