The correct statement about Person Accounts and Contacts is that Person Accounts are appropriate for B2C transactions while Account-Contact model is appropriate for B2B transactions. A Person Account is a type of account that represents an individual consumer, rather than a business or organization. A Person Account combines the features and fields of both the Account and Contact objects, and it does not require a Contact record to be associated with it. A Person Account is suitable for B2C transactions, where the customers are individual consumers who purchase products or services for personal use. An Account-Contact model is a type of data model that represents a business or organization as an account, and its employees or affiliates as contacts. An account can have many contacts associated with it, but a contact can only belong to one account. An Account-Contact model is suitable for B2B transactions, where the customers are businesses or organizations that purchase products or services for professional use. Verified Reference: https://help.salesforce.com/s/articleView?id=sf.accounts_person.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.accounts_contacts.htm&type=5

At minimum, a custom attribute must be created on the Order Item and Order Item Summary objects for the values to automap in Order Management from B2C Commerce Cloud at the order item level. A custom attribute is a field that stores additional information about an object that is not captured by the standard fields. A custom attribute can be created on any object in Order Management, but it must have the same API name and data type as the corresponding attribute in B2C Commerce Cloud. For example, if an order item has a custom attribute called Color in B2C Commerce Cloud, then an Order Item and an Order Item Summary must also have a custom attribute called Color in Order Management for the value to automap. Reference:Order Management Objects, [Custom Attributes]

Three possible causes of this issue are:

The administrator has duplicate Product SKUs in the JSON query. A Product SKU is a unique identifier for a product that is used to track inventory and sales. A Product SKU must be unique within an org, and it cannot be duplicated in a composite API call. If the administrator has duplicate Product SKUs in the JSON query, it will cause an error when loading test orders via the Workbench.

The number of subrequests in the JSON query exceeds the 20 subrequest limit. A subrequest is a single HTTP request that is part of a composite API call. A composite API call can contain up to 20 subrequests in a single JSON body. If the administrator has more than 20 subrequests in the JSON query, it will cause an error when loading test orders via the Workbench.

Record IDs used within the request are incorrect. A record ID is a unique identifier for a record that is used to reference and manipulate data in Salesforce. A record ID must be valid and exist in the org, and it must match the data type and format of the corresponding field. If the administrator has incorrect record IDs in the JSON query, such as using 15-character IDs instead of 18-character IDs, or using IDs from a different org, it will cause an error when loading test orders via the Workbench.

Verified Reference: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite_composite.htm https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/dome_composite_sobject_tree_flat.htm

Three steps that the administrator should take to implement this functionality are:

Create an External Data Source pointing to the external system's database. An External Data Source is a type of metadata that defines the connection and authentication information for an external system that stores data outside of Salesforce. The administrator can create an External Data Source using the Lightning Connect OData 2.0 or 4.0 adapters, which support read-only access to data in relational databases.

Create an External Object for each table of accounting data in the external system. An External Object is a type of custom object that maps to a table in an external system. The administrator can create an External Object for each table of accounting data that they want to access from Salesforce, and define its fields and relationships accordingly.

Create an Indirect Lookup field to connect to the Account. An Indirect Lookup field is a type of custom field that links a child External Object record to a parent standard or custom object record. The administrator can create an Indirect Lookup field on the External Object that references the Account object, and specify the external column name and value that match the Account ID.

Verified Reference: https://help.salesforce.com/s/articleView?id=sf.external_object_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.external_object_relationships.htm&type=5

Dynamic Actions allow an administrator to add visibility rules for the buttons in the Highlights Panel on the Lightning Record Page. Dynamic Actions let you configure when and where actions appear on a record page based on criteria such as record field values, user permissions, or device type.