The best way for the administrator to meet this requirement is to create an External Data Source in

Setup that

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

Two ways that an administrator can query Order Summaries using APIs in Workbench are:

Platform API. The Platform API is a set of REST and SOAP APIs that allow developers to access data

and functionality in Salesforce from external systems. The Platform API includes various resources

and operations for querying, creating, updating, or deleting records in Salesforce, such as Order

Summaries. The administrator can use the Platform API in Workbench by selecting the REST Explorer

or SOAP Explorer tabs, and entering the appropriate request URL and parameters.

Composite API. The Composite API is a type of REST API that allows developers to execute multiple

subrequests in a single HTTP request. The Composite API includes various resources and operations

for batching, tree, sObject collections, or transactions in Salesforce, such as Order Summaries. The

administrator can use the Composite API in Workbench by selecting the REST Explorer tab, and

entering the appropriate request URL and JSON body.

Verified Reference: https://developer.salesforce.com/docs/atlas.enus.api_rest.meta/api_rest/intro_what_is_rest_api.htm

https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite.htm

The best way for the administrator to meet this requirement is to modify the compact layout on the

Credit Memo object. A Credit Memo is a record that represents a refund or credit issued to a

customer for an order or part of an order. A Credit Memo has various fields and related lists that

display information such as the credit amount, status, reason, etc. A compact layout is a type of

layout that determines which fields appear in the highlights panel at the top of a record page in

Lightning Experience or Salesforce mobile app. The administrator can use the Object Manager to

modify the compact layout on the Credit Memo object and add the Total Amount field to the

compact layout. This way, the sales team can see the Total Amount field in the highlights panel at the

top of the Credit Memo record page. Verified Reference:

https://help.salesforce.com/s/articleView?id=sf.order_management_credit_memo.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.compact_layouts_overview.htm&type=5

The feature that supports this use case is the Unmanaged Order Checkbox. This is a standard field on

the Order Summary object that indicates whether the order is managed by Order Management or

not. If this field is checked, then the order is not actioned on by Order Management, and it does not

trigger any flows or processes. The administrator can use this field to import Order Summary records

containing historical data without affecting the order lifecycle. Verified Reference:

https://help.salesforce.com/s/articleView?id=sf.order_management_order_summary.htm&type=5