---
schema_version: "1"
id: 02939fc32480d20c2769de940546fa94dd1b1dc273f7baf6715eb6f5c81c588b
title: Patch Releases (Platform) Winter '27
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_patch_updates_platform_winter_27.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_patch_updates_platform_winter_27.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 218c0c1d4ec00b4053ed998650d4cf1aa2cabc61e831ea99413b4b479e3b83d1
description: This topic provides information on each Winter '27 Patch Release for Industries CPQ product area for the fixes made in Platform.
products:
  - Communications
  - Media
  - Energy and Utilities
release: "264"
---
# Patch Releases (Platform) Winter '27

This topic provides information on each Winter '27 Patch Release for Industries CPQ product area for the fixes made in Platform.

## 264.5

 
| Issue | Description |
| --- | --- |
| During Replace Offer (Change of Plan), the system does not populate the `SubAction__c` field with Reassign on parent and intermediate line items such as Additional Internet Services. The system correctly assigns only leaf-level items and does not create an OrderItemRelationship for the affected items. | The fix corrects the hierarchy processing so that all applicable items are updated with the correct `SubAction__c` field status. |
| Before replacing an offer, the system could treat explicitly disconnected products as Active, reassign them to the new offer, and incorrectly include them in cardinality calculations, resulting in a false cardinality violation message. | Preserves disconnected items during reconciliation so they remain excluded from reassignment and cardinality calculation. |
| In the MACD Cart, the system was marking newly added draft items `Action = Add`) as Disconnected instead of hard deleting them. | The fix removes draft items correctly, while existing items continue to follow the standard disconnect process. |
| Replace Offer could create relationship records that were not relevant to ReliesOn attribute propagation. These records could contain empty identifiers and cause `priceCart` to fail. | Empty identifiers are now handled safely, and error messages identify the correct object when a query fails. |
| When two sibling items under the same parent are auto-removed in a single Standard AddToCart call, the cart UI reflects only one of the two removals. This is caused by a response-parity issue in the `itemdeleted` action node. Standard Cart emits one `itemdeleted` record per auto-removed child and stamps every child slot with the full set of `deletedItemIds`. Classic Cart emits one record per surviving parent carrying all removed subtrees and stamps each slot with only its own `deletedItemIds`. This difference in response shape causes the UI to miss one of the two sibling removals. | Align the Standard AddToCart item deleted response with Classic Cart behavior. Auto-removed siblings are grouped into one record per surviving parent, and each slot is stamped with only its own deletedItemIds. |