--- cuppy_hub: salesforce cuppy_path: reference/official/data360/connectapi/guide/data-stream-use-case.md cuppy_section: docs cuppy_doc: AEKH-CB7Z cuppy_doc_uuid: 250818a3-8f09-42cc-8c45-e3e0c336c14d cuppy_permalink: https://cuppy.io/salesforce/d/AEKH-CB7Z cuppy_version: 1 cuppy_updated: 2026-10-23T16:16:52.575Z cuppy_canonical: https://cuppy.io/salesforce/docs/reference/official/data360/connectapi/guide/data-stream-use-case cuppy_mcp: https://cuppy.io/mcp cuppy_body_sha256: 219d6bd35b57b6ebe61a12498890d1e45b85fd91c3e0ff33a7766062260bd885 # cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks. --- > Mirror of (Salesforce, Data 360 Connect REST API Guide), read 2026-10-23. Salesforce's own page is the authority; this copy exists because that site refuses non-browser readers. ## Data Streams: Bulk Disable Salesforce CRM Fields **Business Goal**: Keep your Salesforce CRM connector data streams healthy by removing fields that are inaccessible or no longer needed. Source fields can become unavailable when a standard field deprecates, a custom field is deleted, or the Platform Integration User (PIU) loses field-level access. When these cases occur, Data 360 repeatedly attempts to extract the field and fails. Disabling the field stops these attempts. Disabling fields one at a time triggers a separate deploy cycle per field, during which no other field operations can proceed. Bulk disabling processes all fields in a single deploy cycle regardless of how many fields you select. **Use Case**: A data stream is in error state because of missing permission or fields in the corresponding CRM org. A data engineer uses the Connect API to identify which fields are affected, then disables them in a single operation. In this example, the engineer disables one standard field (Annual Revenue) and one custom field (Is Enrolled). For limit information, see [Data 360 Limits and Guidelines](https://help.salesforce.com/s/articleView?id=data.c360_a_limits_and_guidelines.htm). ![Image 1: Sequence diagram showing the requests for disabling Salesforce CRM fields with the Data Stream Connect API.](https://a.sfdcstatic.com/developer-website/sfdocs/data-cloud/media/connectapi/data-stream-seq-diag.png) * Don’t disable these critical fields: Id, SystemModstamp, SfdcOrganizationId, DataSource, DataSourceObject, and cdp_sys_PartitionDate. * Before you disable a field, determine whether you can restore field access. For example, check field existence in your source org. * When you disable a field, new data stops populating it. Downstream consumers such as data model object (DMO) mappings, transforms, segments, and activations receive null or stale values. * To re-enable Salesforce CRM disabled fields, use the [UpdateDataStream endpoint](https://developer.salesforce.com/docs/data/connectapi/references/spec#tag/Data-Streams/paths/~1ssot~1data-streams~1%7BrecordIdOrDeveloperName%7D/patch). Find the name value of the fields you want to disable. Use the [get data stream](https://developer.salesforce.com/docs/data/connectapi/references/spec#tag/Data-Streams/paths/~1ssot~1data-streams~1%7BrecordIdOrDeveloperName%7D/get) endpoint to get a list of all fields in your data stream. Pass the record ID or developer name of the data stream in the URL. The API call lists all your data stream fields. To find the `name` property for the relevant fields, open the `dataLakeObjectInfo` section, and then the `fields` section. Under `fields`, note the `name` property value for each field you want to disable. Use this value to bulk disable the fields on Step 2. For standard fields like `IsEnrollmentRequired`, the name value has no suffix. For custom fields like `customField`, it ends in `_c`. Use the [update data stream](https://developer.salesforce.com/docs/data/connectapi/references/spec#tag/Data-Streams/paths/~1ssot~1data-streams~1%7BrecordIdOrDeveloperName%7D/patch) endpoint to disable one or more fields in a single operation. For each field, include the `name` value you obtained in Step 1 as `targetFieldName`, and set `transformationFormula` as null. For custom fields, include the `_c` suffix. In this example, one standard field `IsEnrollmentRequired` and one custom field `customField_c` are disabled. The API returns the updated data stream. The data lake object (DLO) field count remains unchanged. The API removes only the source field link and sets the formula as null. Disabled fields are tagged as **Disabled** in the Data 360 UI. --- You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 376 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/salesforce/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.