---
schema_version: "1"
id: 5273ae5047b2a720714598f6b04018467236b2edc3947ff388ebde0f1255ad1d
title: Remove Non-Public Fields from Custom Object Data in Aura Action Responses (Release Update)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/264-0-0/rn_lc_rus_remove_nonpublic_fields_ru.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_lc_rus_remove_nonpublic_fields_ru.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f7466d516985e8ee544655fa9e6b46558e1b7ea41a9c9fed6a4d84b760d079a5
description: To improve security, Salesforce is removing non-public system fields from custom object data returned in Aura action responses. This update filters out internal system fields that aren’t part of the public Salesforce API. Review your Lightning components that process custom object data to avoid JavaScript errors or missing data. Use only API-supported fields in your components to ensure that your data displays correctly. This update was first available in Summer ’26 and is enforced in Spring ’27
products:
  - Cross Cloud
release: "264"
---
# Remove Non-Public Fields from Custom Object Data in Aura Action Responses (Release Update)

To improve security, Salesforce is removing non-public system fields from custom object data returned in Aura action responses. This update filters out internal system fields that aren’t part of the public Salesforce API. Review your Lightning components that process custom object data to avoid JavaScript errors or missing data. Use only API-supported fields in your components to ensure that your data displays correctly. This update was first available in Summer ’26 and is enforced in Spring ’27

**Where:** This change applies to Lightning Experience in all editions.

**When:** Salesforce enforces this update in Spring ’27. To get the major release upgrade date for your instance, go to [Trust Status](https://status.salesforce.com/), search for your instance, and click the **Maintenance** tab.

**Why:** When Aura actions return custom object records, the response currently includes internal system fields that aren’t part of the public Salesforce API. With this update, those non-public fields are filtered out of the response. Only fields that are part of the supported Salesforce API continue to be returned.

If your Lightning components use internal system fields from custom object data returned by Aura actions, those fields are no longer available after this update is enforced. Affected components may display missing data or encounter JavaScript errors.

**How:** Review your Lightning components that process custom object data to ensure they use only supported, publicly documented fields. Enable the release update in a sandbox environment and test all Lightning components and pages that process custom object data. If you encounter errors, update affected components to remove references to non-public system fields and use only API-supported fields.