---
schema_version: "1"
id: c65b2ec947f9ba5dfa7ff0f7042eb352ba61c58b0d8b332128718610b7b14128
title: Usage Considerations
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/industries/cme/guides/comms-sdc-usage-considerations.md
canonical_url: https://developer.salesforce.com/docs/industries/cme/guide/comms-sdc-usage-considerations.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 32fd8406937926e13580dce3f32e0af2dacf5385c33b00bbc303495e868b22b7
products:
  - Communications, Media, Energy and Utilities APIs (Managed Package)
  - Industries Developer Documentation
---
# Usage Considerations

When using Standard Digital Commerce, note these usage considerations and restrictions.

- Standard Digital Commerce doesn't support the JSONAttribute V1 Schema. Upgrade to [JSONAttribute V2 Schema](https://help.salesforce.com/s/articleView?id=ind.comms_jsonattribute_v2_schema_upgrade_considerations.htm) to use Standard Digital Commerce.
- You cannot create carts using the JSON body. Instead, use `cartContextKeys` to create carts. Before creating carts with `cartContextKeys`, enable `CacheAPI.CreateCartFromContextKey`.
- Standard Digital Commerce doesn't support `DefaultPricingPlanImplementation` and `PricingElementService`. Use `PricingPlanService` instead.
- New cartContextKeys aren't created when you make changes to an existing basket that uses an existing cartContextKey.
- Pseudo Accounts and Orders aren't created.
- The `dc_basket_fs` fieldset is not available with Standard DC.
- The `vlocity_cmt__PricingLogData__c` field does not include the 'AppliedPromotions' node when a promotion is added and an order/cart is created using Standard Digital Commerce. However, this node appears if the order is created and a promotion is applied using the hybrid cart.
- Configure and Basket API responses aren't shared among a group of users when a set of cache records are created. Unlike executing Digital Commerce APIs when Standard Digital Commerce APIs is disabled , there are no cache hit or cache miss operations when Standard Digital Commerce is enabled for Configure and Basket operations.
- Standard Digital Commerce doesn't support deleting by the index [By BundleNumber]. For example: `payload: {"basketAction":"DeleteFromBasket","deleteBundleNumber":"0"}`. For more information on BundleNumber, see [BasketOps](https://developer.salesforce.com/docs/industries/digital-commerce/references/dc-rest?meta=BasketOps).
- Standard Digital Commerce supports the entity filters on these objects:

  - Product

  - PricebookEntry

  - ProductChildItem

- After you enable Standard Digital Commerce, there are changes to the responses of certain API calls. See [Changes to API Responses](https://help.salesforce.com/s/articleView?id=ind.comms_Changes_to_API_Responses.htm&type=5).