---
schema_version: "1"
id: e21b71c25c5975aa2ceb0dce17bd76ae650a18b353cd15629e2e9902490bd4d4
title: Considerations for Processing Objects
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/privacy_center_object_processing.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.privacy_center_object_processing.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c003b8b791a3f21a8b5e8e185f113354ead038e04a6818e3016dfefe452f00f7
description: To achieve your data management goals more effectively, review key concepts around ordering objects and deleting data with privacy policies. And be aware of how errors or missing data can affect your implementation.
products:
  - Security
  - Cross Cloud
release: "264"
---
# Considerations for Processing Objects

To achieve your data management goals more effectively, review key concepts around ordering objects and deleting data with privacy policies. And be aware of how errors or missing data can affect your implementation.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col style="width:100%"></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Developer</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong> Editions. Requires the Privacy Center license.</td></tr></tbody></table>

## Configuring Multiple Objects on a Policy

You can add multiple parent and child objects to a Data Management policy. Parent objects are processed in the order that they appear on the policy details page, under Active Objects. You can adjust the order by using the Up or Down arrow buttons.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-data_protection_and_privacy-264-0-0-production-enus/27d1bf87-a47b-491a-8339-f53ef6540aec/images/icon_note.png)

Note You can only add one parent object to a Right to Be Forgotten (RTBF) policy.

After adding a parent object, you can configure any of its child objects by clicking **Add Child Object**. Child objects are processed before their associated parent object.

## Child Objects and Data Deletion

When you delete data on a parent object, child objects with a master-detail relationship to the parent object are deleted automatically. Child objects with a lookup relationship to the parent object remain in your org, and their parent record fields are set to a null value. To delete child lookup objects, add them to your policy and specify that you want their data deleted.

Policy previews and job metrics capture only the objects that are defined on the policy, as shown under Active Objects on the policy page. Records that are cascade-deleted and not part of a defined object aren’t included in the count of deleted records. To learn more about policy previews and affected records for jobs, see:

- [Preview a Data Management Policy](https://help.salesforce.com/s/articleView?id=xcloud.preview_data_management_policies.htm&release=264.0.0&type=5 "Generate and acknowledge a preview of your Data Management Policy configuration. Previews estimate the number of records and files that are affected by your policy, helping you evaluate its impact on the data in your org.")
- [View and Manage Privacy Jobs](https://help.salesforce.com/s/articleView?id=xcloud.view_policy_job_sessions.htm&release=264.0.0&type=5 "See details about the jobs for your Data Management and Right to Be Forgotten policies. You can also cancel, reschedule, or immediately run privacy jobs.")

## How Errors and Missing Data Affect Object Processing

If a referenced object or field gets removed from your org, Salesforce updates your policy automatically so that it no longer references the missing object or field. Sometimes, a missing field can cause an entire object to be removed from your policy. You’re alerted to the change when you open the policy details page. This behavior is designed as a safety precaution to reduce the risk of unintentionally modifying or deleting records.

If a top-level object has job errors and fails to process, the job stops completely, and the remaining top-level objects and their children aren't processed. This behavior avoids the risk of processing data erroneously, for example updating records that you intended to mark for exclusion in the previous step. If you don’t want to have this safeguard in place, use separate policies to process top-level objects independently.

## Object Processing Limitations

These objects and data types aren't supported in Privacy Center.

- External objects
- Big objects
- Setup objects
- Unstructured data (such as data within an attached PDF)

## Search Layouts in Salesforce Classic

For some objects (for example, contact point address), search layout customizations made in Lightning Experience don’t appear in Salesforce Classic. To view customized search layouts, use Lightning Experience.