Pass the Salesforce B2B-Commerce-Developer B2B-Commerce-Developer Questions and answers with CertsForce

The most likely cause of the custom fields in the Order Summary being empty in the export file is that the developer does not have access to the fields. To export data with Data Loader, the developer must have the View All Data permission and the appropriate field-level security settings for the fields they want to export. If the developer does not have access to the custom fields in the Order Summary object, they will not be able to export them. Option A is incorrect because a misspelling in one of the custom fields would not affect the export of the other two custom fields. Option B is incorrect because the Cart to Order action does support the mapping of custom fields from the Cart object to the Order Summary object. Option D is incorrect because the developer can export Order Summary records by using Data Loader or other solutions, not only by using Data Export Service. References: Export Unmanaged Order Summaries with Data Loader, Data Loader Guide, [Set Field-LevelSecurity]

The format that the custom Salesforce relationship with the API name, My_Relationship_Name__r.My_Name__c is queried and transformed into by default in Salesforce B2B Commerce is myRelationshipName.myName: value. This is done to follow the JavaScript naming convention and to avoid conflicts with the standard Salesforce fields and relationships. The transformation rules are as follows:

Remove any namespace prefix from the field name, suchas ccrz__ or cloudcraze__.

Remove any underscores from the field name and capitalize the first letter of each word after an underscore, such as MyRelationshipName and MyName.

Lowercase the first letter of the field name, such as myRelationshipName and myName.

Use a dot (.) to separate the relationship name and the field name, such as myRelationshipName.myName.

Use a colon (:) to separate the field name and the field value, such as myRelationshipName.myName: value. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Query Transformation

To update the checkout process so that buyers can purchase with one of the below payment types:

Credit Card

Purchase Order

Contract Now & Pay Later Additionally, show only Purchase Order and Contract Now & PayLater if a custom checkbox field on the account is checked, a developer should create a custom Lightning web component for the checkout flow that has all the options available. Within that component, pull data from the account to determine which options toshow. Creating a custom Lightning web component for the checkout flow allows the developer to define custom logic and user interface for processing payments using different payment types. The developer can use Apex methods or third-party APIs to integratewith payment service providers or payment gateways and handle payment authorization, capture, void, and refund. The developer can also use @wire or @api decorators to get data from the account object and use its properties, such as the custom checkbox field, to determine which payment options to show or hide based on business logic. Creating a custom Lightning web component that can be used with the standard payment component is not a valid way to meet this requirement, as it does not allow the developer to replace or modify the standard payment component’s logic or user interface. Modifying the standard payment component settings in the checkout screen flow and adding the new payment method is not a valid way either, as it does not allow the developer to add custom payment types or conditional logic based on account data. Adding a new payment gateway through the reference implementation steps so the payment shows up on the checkout payment screen is not a valid way either, as it does not allow the developerto add multiple payment options or conditional logic based on account data. Salesforce References: B2B Commerce Developer Guide: Payment Integration, B2B Commerce Developer Guide: Payment Component, B2B Commerce Developer Guide: Checkout Subflow

When including additional JavaScript files in a Lightning Web Component, it is required that these files are ECMAScript 6 (ES6) modules and have unique names within the component's folder. This ensures proper module resolution and avoids namespace conflicts. Salesforce LWC documentation provides guidelines on organizing component resources, including JavaScript modules, to ensure they are correctly recognized and utilized within the LWC framework.

Two advantages of using Lightning Data Service are that it combines and de-duplicatesserver calls and that it loads record data progressively. Lightning Data Service is a service that provides access to Salesforce data and metadata in Lightning web components. It optimizes performance and minimizes server round trips by caching data on theclient side and sharing data across components. It also combines and de-duplicates server calls by batching requests for the same record or object and returning a single response. It also loads record data progressively by returning available cached datafirst and then fetching updated data from the server asynchronously. Communicating with other components and converting between different data formats are not advantages of using Lightning Data Service, as they are not related to its functionality or features. Salesforce References: Lightning Web Components Developer Guide: Lightning Data Service, Lightning Web Components Developer Guide: Work with Salesforce Data

The fastest route to setting up a B2B Commerce store as a developer is to use sfdx setup scripts. Sfdx setup scripts arescripts that use Salesforce CLI commands to automate the creation and configuration of a B2B Commerce store. The scripts can perform tasks such as creating scratch orgs, installing packages, importing data, assigning permissions, and deploying code. The scripts can save time and effort for developers who need to set up a B2B Commerce store quickly and easily. Setting up B2B Commerce on Lightning Experience manually is not the fastest route to setting up a B2B Commerce store, as it involves many steps and actions that can be tedious and error-prone. Creating a new store in the Commerce app is not the fastest route either, as it also requires manual configuration and customization of various settings and features. Importing a previously exported store archiveis not the fastest route either, as it depends on the availability and quality of the store archive and may not reflect the latest changes or updates. Salesforce References: [B2B Commerce Developer Guide: Set Up Your Development Environment], [B2B CommerceDeveloper Guide: Create Your Store]

The correct syntax to render a property in a Lightning webcomponent template is to surround the property with curly braces: {property}. This syntax allows you to access the property value from the JavaScript class of the component and display it in the HTML template. The other options are incorrect because they either use invalid characters or do not follow the standard syntax for rendering a property in a Lightning web component template. References: Use JavaScript Properties in Templates | Lightning Web Components Developer Guide

Option B is the correct answer because it describes a way to create a scheduled job in another system to move data into the B2B Commerce org without additional third party tools. The developer can set up an SFTP server as a waystation, drop the files there using the off-platform job and schedule a job in-platform to process the file. This way, the developer can use thebuilt-in integration capabilities of the B2B Commerce platform, such as the Windows Integration Service (WIS) or the Integration Job Definitions, to import the data from the SFTP server into the org. The other options are incorrect because they either require additional third party tools, such as WebDAV or CLI, or they do not create a scheduled job in another system, but rather in the same org. References: Creating and editing integration jobs, Create a B2B Commerce Org andCheckout Flow, B2B Commerce on Lightning Experience Developer Guide, B2B Commerce and D2C Commerce Developer Guide

A valid way of referencing the CC Cart Object whose API name is E_Cart__c in a SOQL query is to useccrz__E_Cart__c. This is the transformed name of the object that is used by the Salesforce B2B Commerce framework. All custom objects and fields that are part of the cloudcraze managed package have the prefix ccrz__ intheir API names. For example, SELECTId, Name FROM ccrz__E_Cart__c will query the CC Cart Object records. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Query Transformation

The sfdx commerce:store:quickstart:setup command allows thedeveloper to set up a store from scratch using a definition file that specifies the store configuration. This command performs the following tasks:

Pushes the store sources to the scratch org

Creates a buyer user

Imports products

Creates a search index

Opens the store in a browser

The other options are not correct because:

A. sfdx commerce:store:quickstart:create only creates a community for the store, but does not perform the other tasks required to set up a store from scratch.

C. sfdxcommerce:store:create creates and sets up a store, but does not use a definition file to specify the store configuration. Instead, it uses command-line flags to provide the store parameters.

D. sfdx commerce:store:open only opens an existing store in a browser, but does not create or set up a store from scratch.

References:

store Commands

Build a B2B and B2B2C Commerce Store