Packing a Sales Order: to perform a pack, by click the down arrow next to Change Owner and selecting Pack SO: You’ll be brought to this screen, which gives you multiple options on how to pack. You can select the Pack button on a single line, if you only wish to pack one line.
Full Answer
How to get started with packaging in Salesforce platform?
Become familiar with CLI commands for packaging. Describe the basic packaging use cases. Package the DreamHouse LWC sample app and install it in a Trailhead Playground. We think packaging is one of the most exciting features for Salesforce Platform developers.
How to create a packing list item component?
Create a Packing List Item Component 1 Create a component called campingListItem that displays the name (ui:outputText) and the three custom fields using the... 2 Add an attribute named item for type Camping_Item__c that is required. More ...
How do I create a global picklist in Salesforce?
Create Picklists and Field Dependencies. Start by creating a global picklist value set called Region. From Setup, enter Picklist Value Sets in the Quick Find box and select Picklist Value Sets. Click New and fill in the details. Field. Value. Label. Region.
What are picklists and field dependencies in Salesforce?
To accomplish what they want, you set up picklists and field dependencies. Picklists offer a selection of options available for specific fields in a Salesforce object, such as a list of regions.
Introduction
Sales Operations divides AW Computing’s sales territory into regions and zones. Yuko Ishikawa would like to be able to identify each account record by its region and zone.
Create Field Dependencies
Create a dependency between these two picklists, so that when a Region is selected, only respective zones are available in the Zone field.
Why We Love Package Development
We think packaging is one of the most exciting features for Salesforce Platform developers. It’s on par with some well-known disruptive innovations, such as sliced bread, the mobile phone, and video streaming services. But just in case you need more convincing, let’s sum up the key benefits that we’ve learned so far. Package development:
Configure Your Environment
Before you can get to the good stuff, let’s set up a new Trailhead Playground and enable the Dev Hub and packaging in it.
Create the Package
When you cloned the DreamHouse LWC app from GitHub, you pulled all the source files into your project directory. You can now create the base package without further fanfare.
Create a Scratch Org to Test Your Package Version
Let’s create a scratch org, in which to install the unlocked package, with the alias MyScratchOrg. Testing in a scratch org is a convenient way to perform the unit testing phase of the packaging development lifecycle.
Create the Package Version and Install It in Your Scratch Org
When you’re ready to release the package, you create a snapshot of it, called a package version. Installing the package version is similar to deploying metadata. Remember, once created, a package version serves as an immutable artifact containing a specific set of metadata.
Release the Package Version
One feature we haven’t discussed yet is package status. Packages have beta status when you initially create them. You can’t install beta packages in a production org. This is a safeguard to make sure the package version you release is production ready.
Install the Package Version in an Org
Last but not least, install the package version in your org. Remember, you can install beta package versions in scratch orgs, sandboxes, and Trailhead playgrounds (DE orgs). You can install a released package version in any org.
