This site contains information to help Salesforce admins to get started with SmallBuilder products.

Installation

SmallBuilder is available for installation directly from the AppExchange.

When you install SmallBuilder, you will get access to the free trial by default. You can implement Line-item Configurators, Document Templates, and Lists with the free trial. However, if you want to set up more than one configuration, you need to purchase a license.

License and Permission Set Assignment

SmallBuilder offers 10 free licenses. Before using the product, ensure that each user has the appropriate SmallBuilder license and permission set assigned for access.

Organization Currency Setup

After an organization is initially created, the currency may be set to null. If the currency is not properly configured, SmallBuilder may not function correctly. Make sure to verify that your organization’s currency is properly set before using the product.

Connected App Configuration

To perform metadata-related tasks, such as adding buttons to page layouts or creating tabs in the builder screen for SmallBuilder, you need to configure the connected app.

After an organization is initially created, the currency may be set to null. If the currency is not correctly configured, SmallBuilder may not function properly. Please ensure the organization’s currency is properly set before using the product.

1. In Setup, enter Company in the Quick Find box, then select Company Information.

2. Click Edit.

3. Under Currency Settings, ensure that a valid currency is selected.

4. If the currency is set to null, select the appropriate currency.

To perform metadata-related tasks, such as adding buttons to page layouts or creating tabs in the builder screen for SmallBuilder, you need to configure the connected app.

Step 1: Configure Permitted Users

1. In Setup, enter Connected Apps in the Quick Find box and select Manage Connected Apps.

2. Click Edit for SmallBuilder {Product Name} OAuth.

3. Set Permitted Users to Admin approved users are pre-authorized.

4. Click Save.

Step 2: Assign Profiles or Permission Sets

1. In Setup, enter Connected Apps in the Quick Find box and select Manage Connected Apps.

2. Click SmallBuilder {Product Name} OAuth.

3. At the bottom, click Manage Profiles or Manage Permission Sets.

4. Select the profile or permission set responsible for configuring the product using the builder.

5. Click Save.

SmallBuilder Line Items provides a Line Item Editor that supports discount calculators and external data integration for both standard objects like Opportunities and Quotes, as well as custom objects. This solution enables seamless implementation without requiring development.

Why Use the Line Item Editor?

In Salesforce, standard objects with junction relationships, such as Opportunities, Quotes, and Orders, are essential in Sales Cloud. While Salesforce provides robust out-of-the-box functionality for adding and modifying line items for these objects, there are some limitations.

For example:

• Total amounts are not automatically calculated when entering sales prices or quantities.

• Users must manually calculate and enter discounts.

• Many users want to reference inventory data from their servers when selecting products or entering line items.

• They also wish to automatically apply account-specific discounts from related objects.

These needs often require developer intervention, making it difficult for admins to customize or update features. With the Line Item Editor, these limitations are addressed using a point-and-click approach:

• Automatic calculations and external data integration can be implemented with minimal development or point-and-click configurations.

• The builder enables easy screen implementation, saving time and simplifying maintenance for feature updates or modifications.

• The basic setup required for implementing the Line Item Editor does not need coding, making it accessible to Salesforce admins with fundamental knowledge.

Standard Screen

In the standard Salesforce screen, total amounts are not automatically calculated when modifying unit prices or quantities after adding products.

Line Item Editor Screen

By re-implementing the standard product editing screen with the Line Item Editor, you can expand functionality to include inventory display, automatic calculations, discount applications, and more.

What is a Junction Object?

The Line Item Editor is built on objects with junction relationships. As previously mentioned, Opportunities, Quotes, and Orders are examples. Let’s explore the structure of Opportunity Line Items:

When adding products to an Opportunity, the PricebookEntry object is required to retrieve product and pricing information. Once products are added, details like sales price and quantity are stored in the OpportunityLineItem object.

The OpportunityLineItem object bridges the Opportunity and PricebookEntry objects, allowing multiple PricebookEntries to be linked to a single Opportunity. Objects that serve this role are referred to as junction objects.

With these relationships in place, the Line Item Editor can be implemented at any time. Within the editor, these objects are referred to as:

• Parent: Opportunity

• Lookup: PricebookEntry

• Line Item: OpportunityLineItem

Key Features

✔️ Support for All Objects

The SmallBuilder Line Items editor supports all objects. This means it can handle line items for not only standard objects like Opportunities or Quotes but also custom objects, eliminating the need for coding.

✔️ Point-and-Click Configuration Tool

The builder simplifies the creation of complex Line Item Editor involving three or more objects, such as Opportunities, Products, and Pricebooks.

✔️ Real-Time External Data Integration

For scenarios requiring real-time external data integration, the Builder supports integration by invoking Apex code for seamless real-time data retrieval.

✔️ CPQ Alternative

The Line Item Editor can apply a discount calculator to currency fields, making it an excellent alternative to CPQ for scenarios where convenient discount calculations are essential.

SmallBuilder Line Items starts with the Builder. Use the Builder to configure a customized Line Item Editor tailored to your needs.

Getting Started with the Builder

Learn how to launch the Builder and explore its components.

Builder Setup Steps

Follow these steps to configure the Builder, from connecting objects to preparing the Line Item Editor for use.

SmallBuilder Line Items offers 10 free licenses. Before using the product, ensure that each user has the necessary SmallBuilder Line Items license and permission set assigned for proper access.

License Assignment

The official SmallBuilder Line Items license must be assigned per user. Follow these steps to assign the license:

1. In Setup, enter Installed Packages in the Quick Find box, and select Installed Packages.

2. Locate SmallBuilder Line Items and click Manage Licenses.

3. Click Add Users and select the desired users.

4. Click Add to complete the license assignment.

Permission Set Assignment

SmallBuilder Line Items provides two permission sets. Be sure to assign the appropriate permission set based on the user’s role. Assigning a permission set is essential to ensure smooth use of the product’s features.

SmallBuilder Line Items Manager

The SmallBuilder Line Items Manager permission set is designed to enable administrators to manage SmallBuilder Line Items comprehensively. Administrators with this permission set can efficiently perform tasks such as configuring the builder and adding line item buttons.

SmallBuilder Line Items User

The SmallBuilder Line Items User permission set is intended for regular users who need to edit line items. It is typically assigned to roles such as sales representatives or project managers responsible for viewing and modifying line item data. This permission set allows users to easily access and update line item information.

To perform metadata-related tasks such as adding buttons to page layouts or retrieving custom labels in the builder, additional configurations for the connected app in SmallBuilder Line Items are required.

Step 1: Configure Permitted Users

1. In Setup, enter Connected Apps in the Quick Find box and select Manage Connected Apps.

2. Click Edit for SmallBuilder Line Items OAuth.

3. Set Permitted Users to Admin approved users are pre-authorized.

4. Click Save.

Step 2: Assign Profiles or Permission Sets

1. In Setup, enter Connected Apps in the Quick Find box and select Manage Connected Apps.

2. Click SmallBuilder Line Items OAuth.

3. At the bottom, click Manage Profiles or Manage Permission Sets.

4. Select the profile or permission set responsible for configuring the product using the builder.

5. Click Save.

To smoothly configure the builder and use the editor in SmallBuilder Line Items, a few initial setup steps are required.

Package Installation

Install SmallBuilder Line Items in your organization from the AppExchange.

Assigning Licenses and Permissions

SmallBuilder Line Items offers 10 free licenses. Before using the product, assign the relevant licenses and permission sets to users for access.

Organization Currency Setup

After an organization is initially created, the currency might be set to null. If the currency is not properly configured, SmallBuilder Line Items may not function as expected. Ensure the organization’s currency is properly set before using the product.

Connected App Setup

To perform metadata-related tasks such as adding buttons to page layouts or retrieving custom labels in the builder, additional configurations for the connected app in SmallBuilder Line Items are required.

The screen ratio supports 100%, 90%, and 80%, with the default set to 100%.

When Screen Ratio is 100%

Displays the standard editor screen.

When Screen Ratio is 80%

If the editor contains many columns, reducing the screen ratio allows you to view more columns on a single screen.

How to Launch the Builder

2. Go to the Line Item Editor tab and click New to launch the Builder.

Builder Layout

The Builder provides key functions like saving, deleting, and creating buttons in the top panel. The left-side panel manages basic settings and label changes, while the right panel offers step-by-step configuration.

The Line Item Editor provides a responsive layout tailored to device types (desktop and mobile). It adjusts the size and structure of the editor to deliver an optimal user experience based on the display environment. While desktops display more comprehensive information, mobile devices offer a simplified view.

If you prefer a simplified, consistent layout across all devices, set the device mode to Mobile. This ensures a streamlined and uniform interface regardless of the device being used.

Desktop View

Mobile View

You can customize the titles for the Lookup Selector and the Line Item Editor to fit your needs when launching the editor.

For instance, if you use multiple editors for the same object but want to display different titles based on the editor’s purpose, you can modify the labels. Additionally, the button label that navigates from the Line Item Editor to the Lookup Selector can also be changed.

These label changes can be easily configured by clicking the labels menu in the side panel.

Changing Titles

Changing Button Labels

Applying Custom Labels

The Default Setting configures essential options for the Builder, including its name, description, and key features such as whether to display data directly in the Lookup Selector or show summaries in the Line Item Editor.

These settings can be configured from the side panel of the Builder.

Settings Available in the Side Panel

Default Setting

Label Setting

After an organization is initially created, the currency might be set to null. If the currency is not properly configured, SmallBuilder Line Items may not function as expected. Ensure the organization’s currency is properly set before using the product.

1. In Setup, enter Company in the Quick Find box, then select Company Information.

2. Click Edit.

3. Under Currency Settings, ensure that a valid currency is selected.

4. If the currency is set to null, select the appropriate currency.

This setting automatically retrieves data when the Lookup Selector screen is loaded. By default, this option is enabled.

Example: When Search All on Load is Disabled

If this setting is disabled, data will not be automatically retrieved upon loading. Instead, records can only be retrieved through keyword searches.

Default (Enabled)

Disabled

This setting allows the same record to be selected multiple times.

Example: Difference Between Standard and Duplicate Selection

Standard Selection

When a record is selected, it is either selected or deselected as usual.

Duplicate Selection

With duplicate selection enabled, selecting the same record multiple times will add it to the line items as many times as it is selected.

Manage settings related to the Line Item Editor, such as displaying summaries at the bottom or fixing the first column.

These settings pertain to the Lookup Selector, allowing you to configure record selection methods and search functionality.

SmallBuilder offers 10 free licenses. Before using the product, ensure that each user has the appropriate SmallBuilder license and permission set assigned for access.

License Assignment

A SmallBuilder license must be assigned to each user individually. Follow these steps to assign a license:

1. In Setup, enter Installed Packages in the Quick Find box, then select Installed Packages.

2. Find SmallBuilder {Product Name} and click on Manage Licenses.

3. Click Add Users to select the users to whom you want to assign the license.

4. Click Add.

Permission Set Assignment

SmallBuilder offers two distinct permission sets. Please assign the appropriate permission set based on the user's role. Assigning a permission set is essential to fully utilize the product's features.

• SmallBuilder {Product Name} Manager

  The SmallBuilder Manager permission set is assigned to users responsible for the overall management of the product. Typically, it is assigned to administrators, who can perform a variety of tasks such as configuring builder settings, adding buttons to line items, and creating tabs from list products.

• SmallBuilder {Product Name} User

  The SmallBuilder User permission set is primarily assigned to sales representatives or project managers. Users with this permission set can view lists and documents implemented with SmallBuilder, as well as add and edit data in line items and schedules.

This setting specifies the number of records displayed per page (or scroll). The default is 50 records per page.

Displays summary information at the bottom of the Line Item Editor.

Example: Displaying the Sum of Total Price Field Values in Line Items

In this case, the total values from the TotalPrice field (column) of all added line items will be summed up and displayed at the bottom of the editor.

Configuration Steps

1. Enable Show Summary in the Line Item Options under the Default Settings.

2. In the Line Item Editor Settings step, enable the summary attribute for the TotalPrice field (column).

Result

When the Line Item Editor is executed, the sum of the total price values for all added data will be displayed at the bottom of the editor.

Fixes the first column when scrolling horizontally in the Line Item Editor. If there are many columns to display, try freezing the first column for better navigation.

Default

When Freeze First Column is Enabled

To implement the Line Item Editor, follow these steps:

The parent object serves as the master object for the line item object, maintaining either a Master-Detail or Lookup relationship. The Line Item Editor is executed from the record page of the parent object. When searching for a parent object in the builder, only objects with child objects can be selected.

The Line Item Editor is launched from the record page of the parent object.

Control the deletion of saved line items based on their status by specifying a Boolean field that determines whether deletion is allowed. If the specified field value is true, the delete button will be disabled for the corresponding line item.

Example: Restrict Deletion of Approved Opportunity Products

For Opportunity Products linked to an Opportunity, deletion should be restricted when the product is in an approved state. To configure this, the Approved__c field is used to control deletion.

Builder Setup

Set the Approved__c field as the deletion control field in the builder. Enter the API name of the field into the Deletion Control Field setting.

Result

When the Approved__c field value is true, the delete button is hidden, preventing deletion of the corresponding line item.

The first step in configuring the builder is to define the relationships between the objects that will be used in the Line Item Editor. These relationships must follow a Junction object structure, requiring the configuration of Parent, Line Item, and Lookup objects.

Configuration Steps

Example: Reconfiguring the Opportunity Product Editing Screen

To manage multiple products related to an Opportunity, the OpportunityLineItem object is used. This object references PricebookEntry to retrieve product and pricing information. Using SmallBuilder Line Items, we will reconfigure this standard Opportunity Product registration screen.

• Parent Object: Opportunity Serves as the parent object linking multiple products and maintains a Master-Detail relationship with OpportunityLineItem.

• Line Item Object: OpportunityLineItem Stores product-related data such as sales price, quantity, and total amount and is linked to the Opportunity.

• Lookup Object: PricebookEntry Retrieves product names and pricing information and is referenced by OpportunityLineItem through a Lookup relationship.

The Lookup Object is referenced by the Line Item Object, allowing users to select lookup records that serve as the basis for creating line item records.

The line item object is responsible for selecting reference data, adding additional details, and saving the information. This object must be a child of the parent object. When the parent object is selected in the builder, associated child objects can be searched and selected. This step also provides settings for filters, sorting, auto-numbering, and more.

Configure filters and sorting to display specific saved line items that meet certain conditions when the Line Item Editor is executed. These settings help you display only the desired data and control the order in which it is retrieved.

Set Filters

When the editor is executed, you can filter the saved line item data to display only the records that match specific conditions. Filters follow the same logic as the WHERE clause in SOQL.

For instance, if you want to use the editor to manage Opportunity Products divided into regular and subscription-based products, you can apply filters to each editor. For an editor handling subscription-based Opportunity Products, you can filter records where the custom field Type__c equals ‘Subscription’ by writing the filter as follows:

Type__c = 'Subscription'

You can also use the Query Wizard to generate the filter automatically, without manually writing it.

Set Sorting

You can sort saved line item data in the desired order when the editor is executed. Sorting follows the same logic as the ORDER BY clause in SOQL.

For example, to sort line items by their creation date in descending order, use the following setting:

CreatedDate DESC

Configuration Based on Parent Object

The builder provides automatic configuration support specifically for standard Opportunity, Quote, and Order objects. If the parent object is one of these, you can choose between the following two configuration methods:

Standard: Automatic Configuration

This option is available exclusively for standard objects such as Opportunity, Quote, or Order. It enables automatic setup of required configurations for the Line Item and Lookup objects, allowing for rapid configuration without manual effort.

Example: Automatic Configuration for Opportunity

When you apply standard settings for the Opportunity parent object, the following are configured automatically:

• Line Item Object

  • Configured as OpportunityLineItem

  • Essential fields such as Unit Price, Quantity, and Total Price are automatically added.

• Lookup Object

  • Configured as PricebookEntry

  • Fields required for Lookup (e.g., Product Name, Unit Price) and filter conditions (e.g.m Pricebook2Id) are automatically set.

Manual Configuration: Customize Your Line Items

If your parent object is a custom object or you prefer custom setup, choose Manual Configuration.

Manual Configuration options include:

Start by selecting the parent object, then move to the child object (line item), and finally configure the lookup object that the line item refers to. When defining the lookup object, you must select the field in the line item that references the lookup object.

How to Set Up the Lookup Object

Let’s assume you are setting up the builder for OpportunityLineItem based on the Opportunity object. As shown in the object structure diagram below, OpportunityLineItem has two key relationships:

• Opportunity The parent object of OpportunityLineItem, referenced via the OpportunityId field.

• PricebookEntry The object referenced by OpportunityLineItem for product and pricing information, linked via the PricebookEntryId field.

Step 1: Select the Parent Object

Choose Opportunity as the parent object.

Step 2: Select the Line Item Object

Choose OpportunityLineItem as the line item object.

Step 3: Define the Lookup Object

Since OpportunityLineItem references PricebookEntry, select the PricebookEntryId field in the line item object as the lookup reference field.

If you want to skip the lookup selector and directly transition to the Line Item Editor, activate the Block Lookup Selector feature. Additionally, you can block the lookup selector based on specific conditions.

To set blocking conditions, use a specific field from the parent object as the control field. This field must be of the Boolean type, and if the value is true, the lookup selector will be blocked.

Example: Blocking Product Addtion for Renewed Opportunities

In the Line Item Editor, product addition (line item addition) is blocked for renewed opportunities. In this example, the IsRenewed__c field in the Opportunity object is used to define the blocking condition.

When the IsRenewed__c field is set to true, the button to transition to the lookup selector screen will not be displayed in the editor.

x`Configure filters to load specific records of the lookup object that meet defined conditions, and set sorting options to arrange the records in the desired order when the Lookup Selector screen loads.

Set Filters

Filters ensure that only records meeting the specified conditions are displayed when the Lookup Selector is loaded. The filter configuration follows the syntax of a SOQL WHERE clause.

For example, to display only active PricebookEntry records, you can write:

IsActive = true

Additionally, you can use the Query Wizard to automatically generate filters without manually writing them.

Set Sorting

Sorting ensures that the data appears in the desired order when the Lookup Selector screen loads. The sorting configuration follows the syntax of a SOQL ORDER BY clause.

For example, to sort PricebookEntry records by name in ascending order, you can write:

Name ASC

This setting ensures that the filter search layout is displayed in an expanded state by default. If you frequently use filters, enabling this feature can enhance usability.

Example: When Expand Filters by Default is Enabled

When the Lookup Selector loads, the filter search layout will be displayed in an expanded view by default.

Default (Disabled)

Enabled

Configure the target fields to be searched when entering a keyword. By default, the Name field is set as the target field, and the matching condition is Contains.

Example

The keyword search field is set to the Name field of the PricebookEntry object. The search condition is Contains, meaning that records where the product name includes the entered keyword will be retrieved.

In the editor’s lookup selector screen, if you type ‘Gen,’ only records with ‘Gen’ included in their product name will be displayed.

Configure the alignment of column values. There are three alignment options: left, right, and center. The default alignment is set to left.

Caching enhances performance by enabling faster data retrieval and providing a more stable environment. However, cached data may not reflect recent changes immediately.

To register a line item, you first need to search for a lookup object, such as a product, select the desired record from the search results, and configure details like quantity to complete the registration. The lookup selector setup allows you to configure the layout of search results for lookup object queries.

Configure the fields (columns) to be displayed in the lookup selector. You can also add virtual columns to display data retrieved from DataSources.

Steps to Configure

In the Lookup Selector Setup step, click the Add Column button to select the fields to be displayed in the lookup selector.

Example: Adding Columns

You can rearrange the order of added columns by using the Drag & Drop functionality.

Steps Reorder Columns

2. While holding the mouse button, drag the column to the desired position and drop it.

Example: Changing Column Order

Configure the properties of the fields used in the Line Item Editor. For each selected record from the Lookup Selector, define attributes such as price, discount rate, quantity, and more.

Create virtual columns to store temporary values for displaying data retrieved from a DataSource. Virtual columns can be added by clicking the Add Virtual Column button and support value types such as text, number, and currency.

You can configure the alignment of column values. There are three alignment options: Left, Right, and Center. The default alignment is Left.

Example of Text Alignment

You can assign default values when adding Line Items. Default values can only be set for text or numeric fields.

Example: setting the Quantity Default Value to 1

In the builder, set the default value for the quantity field (column) to 1.

When adding a Line Item, the quantity will automatically be assigned a value of 1.

By default, Line Item fields accept input except for formula fields. However, fields intended for data display purposes should be set to Read-Only.

Example of Setting a Field to Read-Only

Conditional Read-Only

Fields can be set to read-only based on specific conditions through the Advanced Read-Only Settings in the field’s advanced settings menu. For more details, refer to the Set Read-Only Based on Specific Conditions guide.

You can change the order of the added columns using Drag & Drop functionality.

Steps to Reorder Columns

2. While holding down the mouse button, drag the column to the desired position and release.

Example: Reordering Columns

Configure the fields (columns) to be displayed and worked on in the Line Item Editor.

Steps to Add Columns

In the Line Item Editor Setup step, click the Add Columns button.

Example: Adding Columns

When adding Line Items, you can assign specific field values from the Parent Object or Lookup Object as default values.

Example: Assigning Unit Price from PricebookEntry as Default Value for Opportunity Products

When adding Opportunity Products, assign the selected product’s Unit Price as the default value for the Unit Price field in the Line Item.

The Line Item includes both List Price and Unit Price fields. These fields will be populated with values from the Unit Price field in the Lookup Object (PricebookEntry).

Configuration Steps

1. In the source field setting for List Price and Unit Price, select Lookup as the first option.

2. For the second option, select Unit Price.

Result

The selected products’ Unit Price is assigned as the default value to the List Price and Unit Price fields in the Line Item.

You can fix the width of a column. The unit of measurement is pixels (px).

Example of Column Width Adjustment

As shown in the image below, the widths of the Sales Price and Quantity columns are uneven, making the table visually unbalanced. To improve the appearance, you can adjust the column widths to ensure uniformity.

In the builder, set all columns to a width of 180px, except for the Lookup Column(PricebookEntryId).

Result

You will notice that the column widths now appear more stable and uniform compared to before.

Auto-numbering can be configured for line items upon saving. This feature is particularly useful when managing product options, as it helps to differentiate and organize each line item effectively.

Example: Assigning Auto-Numbering to Opportunity Products with Product Options

Suppose you are saving opportunity products through the Line Item Editor on the Opportunity detail page, generating a quote from the opportunity, and syncing the updated data back to the opportunity. If the SortOrder field is not properly saved, line items for product options may appear in the wrong order, causing confusion for users. To address this, you can assign auto-numbering to the SortOrder field, ensuring correct ordering during syncing.

Builder Setup:

1. In the Relate Objects step of the builder, enter the API name of the SortOrder field in the Auto-Number Field setting.

2. To display the sort order, add the SortOrder field in the Line Item Editor Setup step.

Result:

When you launch the Line Item Editor, you will see auto-numbered values in the Sort Order(SortOrder) column.

The Hidden Setting for columns in the Line Item Editor is primarily used for the following scenarios:

Handling Field Values for Calculations

When specific field values are required for advanced calculations, these fields must be included in the Line Item columns. However, users may not need to see all of these fields on the screen. By using the hidden setting, these fields can be excluded from display while still being available for calculations.

Preventing Formula Field Errors

Formula fields in the Line Item object are recalculated during save operations. If a formula depends on a field with a null value, it may result in an error. To prevent this, the hidden setting ensures that required fields are added to the columns and assigned appropriate values without being visible to users.

Designate a Line Item field input as required to ensure users provide the necessary information.

Example: Setting a Field as Required

Fields designated as required are marked with a red line on the left side of the input box.

If a required field value is not entered before saving, an error message will be displayed as shown below.

Before using the Line Item Editor, you can preview how the settings configured in the builder will appear and function within the editor.

Example: Preview

Once the builder configuration is complete and you have verified its functionality through the preview, activate the builder to make the editor ready for use. The editor cannot be used unless the builder is activated.

Activation is required to add the editor button.

Configure fields to display totals at the bottom of the Line Item Editor.

Example: Displaying the Total Summary of TotalPrice

In the builder, check the Summary option for the TotalPrice field.

The total sum of TotalPrice is displayed at the bottom of the editor.

If you want to simply fetch related object data, consider using Basic DataSource settings. You can select an object related to Lookup or Line Item and map the fields of the retrieved object to the Lookup or Line Item fields via DataSource.

Basic DataSource Settings

Actions

Actions involve mapping the data fetched from the DataSource to the fields in Lookup or Line Items. Through these actions, the DataSource values are applied to the designated fields.

Example

When the Lookup Object is set to Product2, users often want to display UnitPrice information. However, in Salesforce, the UnitPrice is stored in the PricebookEntry object, which is a child object of Product. Since UnitPrice cannot be fetched via a formula field, we use a DataSource to query the related PricebookEntry data.

1. In the DataSource settings, specify the Source Object as PricebookEntry.

2. (optional) Click Query Wizard to set up the query conditions: IsActive = true AND Pricebook2Id = {$Parent.Pricebook2Id}

3. To match the PricebookEntry data to the Products, use the following settings:

   • Source Field: Product2Id

   • Target Field: Id

   • Key: true

4. • Source Field: UnitPrice

   • Target Field: SBLI_Virtual1

In cases where the Line Item Editor is configured based on Opportunity Products, you might want to display both the Unit Price and Total Price fields. While both fields are editable in Opportunity Products, they cannot be saved simultaneously because the Total Price is automatically calculated and stored based on the Unit Price and Quantity.

It may seem sufficient to set the Total Price field to read-only. However, since the Line Item Editor relies on builder settings, a field marked as editable will still attempt to save internally, even if it appears read-only on the screen.

To ensure that fields like formula fields or other read-only fields are not saved, you must explicitly activate the Do Not Save setting for these fields.

You can set up DataSources when you want to show data from other related objects, or from external systems in addition to fields from the Lookup or Line Item objects.

Adding a DataSource in the builder

1. If you're setting up a DataSource for a Lookup object, go to the Setup Lookup Selector step. If you're setting up a DataSource for a Line Item object, go to the Setup Line-item Editor step.

2. Click the Add data sources button to open the DataSource editing layout.

DataSource types

Basic DataSources are used when you want to look up related objects in Salesforce to present data together.

For example, if the Lookup object is specified as Product2 and you want to display the unit price from a PricebookEntry, you can use an internal data source to look up the PricebookEntry that meets the criteria, and display the product and unit price together.

Advanced DataSources are mostly used when you want to retrieve data from an external server and display it together with data from the Parent, Line Item or Lookup objects. Since the data is retrieved using a user-created Apex Class, it has the advantage of being able to retrieve data more freely than with internal Salesforce data sources.

For example, if you want to fetch real-time inventory numbers from an external server or ERP system, then you can write Rest API code in an Apex Class and point it to an external data source. Then, you will be able to view that data in the Line Item Editor.

Execution Order of DataSource

The DataSource executes in the following sequence: Basic first, followed by Advanced.

Purpose of Cloning

The cloning feature serves two primary purposes:

1. Safe Modifications and Testing

Since version control is not supported, cloning the current settings allows you to make modifications and test safely. This ensures that you can experiment with changes without affecting the original setup.

2. Quick Implementation of Similar Editors

When you need to create additional Line Item Editors with similar configurations, cloning helps you quickly set up and adjust new editors.

How to Clone

1. Click the Clone button at the top of the Builder.

2. Make any additional settings or modifications on the cloned builder screen.

3. Click Save to complete the cloning process.

Use the Advanced DataSource feature when you need to fetch data from external API servers or perform complex logic for data retrieval and merging. To set up Advanced DataSource, you must write an Apex Class. This approach provides greater flexibility compared to the Basic DataSource for fetching and processing data.

STEP 1: Implement the Interface for Writing an Apex Class

To use an Apex Class with Advanced DataSource, you must implement the SBLI.DataSourceService.Fetchable interface.

This interface includes the execute method, where you implement logic for processing data and returning an SBLI.DataSourceService.Result object. The result contains mapping information between the fetched data and the Lookup or Line Item objects.

Example Code

The following example assumes an external API is called to retrieve inventory quantities by product code. The data is then mapped to the Inventory__c field in the Lookup or Line Item object.

global class DataSourceInventory implements SBLI.DataSourceService.Fetchable {
    global SBLI.DataSourceService.Result execute(SBLI.DataSourceService.Parameter params) {
        // Fetch parent record
        SObject parentRecord = params.getParentRecord();

        // Fetch lookup records
        List<SObject> lookupRecords = params.getLookupRecords();
        
        // Fetch data from external API (e.g., inventory information)
        // Key: Product Code, Value: Inventory Quantity
        Map<String, Integer> inventoryData = new Map<String, Integer>(); 
        inventoryData.put('Product001', 10);
        inventoryData.put('Product002', 20);

        // Create result object
        SBLI.DataSourceService.Result result = new SBLI.DataSourceService.Result();

        // Map DataSource values to Lookup/Line Item objects
        for (String productCode : inventoryData.keySet()) {
            SBLI.DataSourceService.Action action = new SBLI.DataSourceService.Action();
            action.setKeyValue(productCode); // Set Key value for mapping with Lookup/Line Item records
            action.putSourceToTargetField(
                inventoryData.get(productCode), // DataSource value: inventory quantity
                'Inventory__c'                 // API name of the target field in Lookup/Line Item
            );
            result.addAction(action); // Add Action to the result
        }
        
        return result; // Return result
    }
}

// Fetch parent record
SObject parentRecord = params.getParentRecord();
// Fetch lookup records
List<SObject> lookupRecords = params.getLookupRecords();

Map<String, Integer> inventoryData = new Map<String, Integer>(); 
inventoryData.put('Product001', 10);
inventoryData.put('Product002', 20);

// Create result object
SBLI.DataSourceService.Result result = new SBLI.DataSourceService.Result();

// Map DataSource values to Lookup/Line Item objects
for (String productCode : inventoryData.keySet()) {
    SBLI.DataSourceService.Action action = new SBLI.DataSourceService.Action();
    action.setKeyValue(productCode); // Set Key value for mapping with Lookup/Line Item records
    action.putSourceToTargetField(
        inventoryData.get(productCode), // DataSource value: inventory quantity
        'Inventory__c'                 // API name of the target field in Lookup/Line Item
    );
    result.addAction(action); // Add Action to the result
}

SBLI.DataSourceService.Parameter

An object containing information about the parent and lookup parameters configured in the builder.

Example Code

global SBLI.DataSourceService.Result execute(SBLI.DataSourceService.Parameter params) {
    SObject parentRecord = params.getParentRecord();
    List<SObject> lookupRecords = params.getLookupRecords();
    ...
}

Methods

SObject getParentRecord()

Returns the parent record. If no parent parameter is configured in the builder, the value is empty.

List getLookupRecords()

Returns the lookup records. If no lookup parameter is configured in the builder, the value is empty.

SBLI.DataSourceService.Result

An object that contains all mapping information between the DataSource and the Lookup or Line Item objects, which is returned to the editor.

Mapping information is stored in SBLI.DataSourceService.Action objects, which are then added to the SBLI.DataSourceService.Result object and returned.

Example Code

SBLI.DataSourceService.Result result = new SBLI.DataSourceService.Result();
for (String productCode : inventoryData.keySet()) {
    // Store mapping information in the SBLI.DataSourceService.Action object
    SBLI.DataSourceService.Action action = new SBLI.DataSourceService.Action();
    action.setKeyValue(productCode);
    action.putSourceToTargetField(
        inventoryData.get(productCode), // DataSource value
        'Inventory__c'                 // Field API name
    );
    result.addAction(action); // Add the Action to the Result
}
return result;

Methods

addAction(SBLI.DataSourceService.Action action)

Adds an Action object containing mapping information to the Result object.

SBLI.DataSourceService.Action

An object that stores mapping information between the Lookup or Line Item and the DataSource values.

Example Code

SBLI.DataSourceService.Result result = new SBLI.DataSourceService.Result();
// Iterate over product codes and inventory data in the DataSource
for (String productCode : inventoryData.keySet()) {
    SBLI.DataSourceService.Action action = new SBLI.DataSourceService.Action();
    // Map the product code to the Lookup/Line Item Key
    action.setKeyValue(productCode);
    
    // Map inventory data to the Inventory__c field in the Lookup/Line Item
    action.putSourceToTargetField(
        inventoryData.get(productCode), // DataSource value: inventory quantity
        'Inventory__c'                 // Field API name
    );
    result.addAction(action); // Add mapping information
}
return result; // Return the final result

Methods

setKeyValue(Object keyValue)

Sets the DataSource Key value that matches the Lookup or Line Item Key.

putSourceToTargetField(Object sourceValue, String targetFieldApiName)

Assigns the DataSource value to the specified Lookup or Line Item field.

STEP 2: Advanced DataSource Configuration

After selecting the Apex Class, specify the fields to be passed as parameters if the class requires parent or lookup information.

You can leverage the Add Button feature at the top of the builder to add the implemented Line-Item Configurator to the Parent object's page layout.

This button will appear on the Parent object's page in Salesforce so that users can launch the Line-Item Configurator that you have set up.

Create Button and Assign to Page Layout

Button's Aura Component

When the Line Item Editor button is created in the builder, an Aura Component like the one below is automatically generated. If you want to customize how the button invokes the editor, you can modify the Aura Component.

The Product Option feature allows you to add sub-options to a line item, making it possible to register and manage components of a specific product (e.g., additional services, accessory products). This is particularly useful when handling product configurations.

Configuring Product Options

To use the Product Option feature, first activate it in the builder and configure the required settings and data. Follow the setup procedures outlined in the reference documentation:

View Product Option Setup Procedures >

Display and Storage of Line Item Option Values

Learn how product options are displayed and stored in line items:

View Display and Storage Methods >

To set up and use the Product Option feature, follow these steps:

To use the Product Option feature, it must be activated in the builder. This setting can be enabled in the Lookup Object section during the object connection stage.

Standard Objects Only

As noted earlier, the Product Option feature is available exclusively for standard objects such as Opportunity, Quote, and Order.

This limitation exists because Product Options rely on PricebookEntry to retrieve product and pricing information. Since Salesforce only establishes a direct relationship between PricebookEntry and these objects (Opportunity, Quote, and Order), the feature is restricted to them.

Once Product Options are activated, a “Product Option Settings” step is added to the top of the builder. In this step, you can configure the settings required to use the Product Option feature.

Product Option Settings

Product Option settings are divided into two main categories:

Line Item Settings allow you to configure how configured product line items and option product line items are connected and how option information is mapped to line item fields.

Parent Line Item Field

Set the field that connects the line items of configured products to their option line items. This field must be a self-relationship field, which represents a relationship within the same object, allowing one record to reference another record in the same object.

Example

If the Parent Line Item Field is set to Base Line Item for Option (SBLI__BaseLineItemForOption__c), a self-relationship structure is created, enabling option records to reference their configured product record through this field.

Example in the Line Item Editor

Mapping Option Values to Line Item Fields

Configure which line item fields will store the information of selected options. The following option values can be mapped:

Example

for Opportunity Products, the following mappings might be configured:

Example in the Line Item Editor

For the configured product “Desktop PC Intel i3”, the RAM option “RAM 8GB” is selected. The option has a quantity of 1, with a list price and unit price of $45 each.

The values for quantity, list price, unit price, and total price are mapped to their respective fields, as configured.

SmallBuilder Lists offers 10 free licenses. Before using the product, ensure that each user has the appropriate SmallBuilder license and permission set assigned for access.

🔸 License Assignment

A SmallBuilder license must be assigned to each user individually. Follow these steps to assign a license:

1. In Setup, enter Installed Packages in the Quick Find box, then select Installed Packages.

2. Find SmallBuilder Lists and click on Manage Licenses.

3. Click Add Users to select the users to whom you want to assign the license.

4. Click Add.

🔸 Assigning Permission Sets

SmallBuilder Lists provides two permission sets tailored for different user roles. Be sure to assign the appropriate permission set to each user to ensure smooth access to the product’s features.

✅ SmallBuilder Lists Manager

The SmallBuilder Lists Manager permission set is designed for administrators who need to manage the product. With this permission set, admins can configure List Builder settings, create list tabs, and manage other administrative tasks with ease.

✅ SmallBuilder Lists User

The SmallBuilder Lists User permission set is intended for general users who need to view lists. This permission set enables users to access and view the configured lists easily.

Example: Changing the Label of the Lookup Selector Button in the Editor

When the lookup object is set to Pricebook Entries, the name of the lookup selector button displayed in the editor automatically inherits the object name. However, such button names may appear awkward to users. Changing the object label in Salesforce settings is inefficient because the object is used in multiple contexts, potentially impacting other screens.

Steps to Configure:

1. Navigate to the Labels menu in the side panel.

3. Select the preconfigured custom label “Add Products (SmallBuilder_AddProducts)” from the modal window.

4. Confirm that the selected custom label is applied to the input field.

5. Run the editor and verify that the lookup selector button label displayed in the editor reflects the updated custom label.

Result

The custom label will be translated and displayed in the editor based on the user’s language settings.

Example of Custom Label Translations for “Add Products (SmallBuilder_AddProducts)”:

When the user’s language is set to Korean, the button label displayed in the editor shows as “제품 추가”.

When the user’s language is set to English, the button label displayed in the editor shows as “Add Products”.

Product Option data is managed using two objects: Product Feature (SBLI__ProductFeature__c) and Product Option (SBLI__ProductOption__c). Both objects reference the Product (Product2) object and serve the following purposes:

• Product Feature: An optional object used to group product options into categories.

• Product Option: The primary object for managing option products and their related information.

While the main focus is on configuring data in the Product Option object, the Product Feature object can be used additionally if needed for grouping purposes.

Product Feature

The Product Feature object allows you to group product options by category.

Object

Fields

Product Option

The Product Option object is the core component for managing option products and their associated details.

Object

Fields

Default Settings in the Product Option Settings step allow you to configure how product options behave when products are added or viewed in the Line Item Editor.

Unfold by Default

When the Line Item Editor loads, option line item lists for configured products are automatically unfolded to display all added options.

If you want to hide the option lists upon loading, deactivate the “Unfold by Default” setting.

Example

Unfold by Default Activated

Options are visible upon editor load.

Unfold by Default Deactivated

Skip Options Selection

When Product Options are enabled, selecting a product through the lookup selector typically includes an additional step for selecting options. By activating the “Skip Option Selection” setting, you can bypass this step, allowing the product to be added directly.

However, options can still be selected or modified later in the Line Item Editor.

Example

Default Behavior

The option selection step appears after selecting a product.

Skip Option Selection Activated

Activating the “Skip Option Selection” setting skips the option selection step after selecting a product, as shown in the image below. Even if this step is skipped, you can still select or add options later in the Line Item Editor.

Option Filters

Options are retrieved based on the selected product and the Pricebook (Pricebook2Id) of the parent object, such as Opportunity, Quote, or Order.

If you want to add additional criteria for retrieving options, you can configure Option Filters. These filters follow the SOQL WHERE clause syntax and are applied to the Product Option object (SBLI__ProductOption__c).

Example Filter:

IsActive__c = true

Using Query Wizard

The display and storage of option values in line items depend on specific option values and the fields configured in the Line Item Editor setup.

Display of Specific Option Values

Example

For an option with a quantity of 2 and a total price of $90, the calculation works as follows:

Display and Storage Based on Line Item Column Settings

If an option value is mapped to a field that has been added as a column in the Line Item Editor, its display and storage behavior follow the column’s configuration:

• If the column has the “Do Not Save” setting enabled, the value will not be stored in the database, even though it is displayed in the editor.

• Fields not added as columns in the Line Item Editor will not be displayed in the editor but will still be stored internally.

Example: Total Price Field with "Do Not Save" Enabled

In this scenario, the Total Price field is mapped to the TotalPrice field in the line item but is configured with the “Do Not Save” setting in the editor:

The option’s total price is mapped to the line item’s TotalPrice field.

When the option is added and saved, the TotalPrice field is not stored due to the “Do Not Save” setting.

You can fix the column width in the Lookup Selector’s data table. The unit for width is specified in pixels (px).

For metadata-related operations like creating and managing tabs within SmallBuilder Lists, additional configurations for the connected app associated with SmallBuilder Lists are required.

🔸 Step 1: Configure Permitted Users

1. In Setup, enter Connected Apps in the Quick Find box and select Manage Connected Apps.

2. Click Edit for SmallBuilder Lists OAuth.

3. Set Permitted Users to Admin approved users are pre-authorized.

4. Click Save.

🔸 Step 2: Assign Profiles or Permission Sets

1. In Setup, enter Connected Apps in the Quick Find box and select Manage Connected Apps.

2. Click SmallBuilder Lists OAuth.

3. At the bottom, click Manage Profiles or Manage Permission Sets.

4. Select the profile or permission set responsible for configuring the product using the builder.

5. Click Save.

SmallBuilder Lists offers a powerful and flexible record listing feature. This system enables users to create and manage customized lists tailored to their needs by leveraging various data sources. It supports a wide range of filtering options and actions, making it highly adaptable. With SmallBuilder Lists, users can quickly address complex business requirements and make effective, data-driven decisions.

🔸 Why Choose SmallBuilder Lists?

Salesforce provides basic List Views for each object, which are essential for viewing data but come with significant limitations:

1. Limited Button Creation

In Standard List Views, buttons can only be implemented using URL or Visualforce Page formats, except for cases involving record creation or updates. For example, adding a button to generate orders by selecting multiple products in a product list requires using a URL format, which often involves additional configurations in the Flow itself, making the implementation complex and cumbersome.

2. Lack of Data Export Functionality

The lack of a data export feature is a limitation. Currently, it is not possible to export the data retrieved in lists to Excel. While this is a feature frequently requested by many clients, it requires additional development at this time. This inconvenience has been a longstanding concern for users.

3. No External Data Integration

Integration with external data is not supported. In the Standard List View, it is not possible to directly access real-time data from external systems such as ERP.

SmallBuilder Lists addresses these limitations by offering advanced features, as well as highly requested features like Excel export and real-time integration with external data. Additionally, its intuitive Point & Click List Builder allows anyone to implement advanced features without requiring development skills.

🔸 Key Features of SmallBuilder Lists

The key features of SmallBuilder Lists are as follows:

✅ Point & Click Configuration Tool

Admins can effortlessly configure filters, action buttons, and columns using the Point & Click interface. Real-time previews during setup allow users to see the results of the list configurations instantly.

✅ Versatile Action Buttons

SmallBuilder Lists supports multiple button types, including New, Delete, Flow, and URL. By adding Flow buttons, users can create buttons with a wide range of functionalities.

✅ Data Export (Excel)

Up to 50,000 searched records can be exported to Excel. This feature can be enabled or disabled in the List Builder, providing flexibility based on business needs.

✅ Advanced Filtering Options

Filters based on fields from the selected object allow users to extract and view only the records they need.

✅ Related Object and Real-Time External Data Integration

Whether internal or external, data scattered across multiple systems can be seamlessly viewed in one place using the Data Source feature.

This feature consolidates data from different sources into a single view, much like replacing multiple small windows with one comprehensive, panoramic view.

Adding the component yourself

If you want to call the Line Item Editor from somewhere other than the button, you can insert <SBLD:LineItemConfigurator /> as shown below.

<aura:component implements="force:lightningQuickActionWithoutHeader,force:hasRecordId" >   
    <SBLI:LineItemConfigurator 
        builderId="XXX..." 
        recordId="{!v.recordId}" />
</aura:component>

Aura Component Attributes

The core feature of SmallBuilder Lists, the List Builder, provides a powerful and user-friendly interface for creating List Configurators. The List Builder is designed to be intuitive and efficient, enabling anyone to easily create and configure lists. Once a list configurator is created using the List Builder, it is converted into a tab and integrated into the user interface, allowing users to easily access and utilize the new list functionality in a familiar environment.

🔸 Creating and Configuring a List Configurator

1. Navigate to the List Configurator tab in the SmallBuilder Lists app.

2. Click the New button to open the List Builder interface.

3. Configure all necessary elements in the List Builder. Once the configuration is complete, click the Active button to activate the List Configurator.

4. Click TABS to add and manage the tab for the configurator.

Learn more about List Configurator Setup >

🔸 Overview of the List Builder Interface

The List Builder interface is divided into four main sections:

Follow these steps to configure and implement a List Configurator using the Builder:

If you want to cancel unsaved changes and restore the builder settings to their original state, use the Reset feature.

After an organization is initially created, the currency may be set to null. If the currency is not correctly configured, SmallBuilder Lists may not function properly. Please ensure the organization’s currency is properly set before using the product.

1. In Setup, enter Company in the Quick Find box, then select Company Information.

2. Click Edit.

3. Under Currency Settings, ensure that a valid currency is selected.

4. If the currency is set to null, select the appropriate currency.

The Default Setup panel allows you to configure the fundamental details for the list, such as its title, object, and description. It also lets you enable or disable features like exporting and importing records to and from Excel.

The Datatable Setup allows users to configure and manage the data table displayed in the list with precision and flexibility. This feature enables users to customize how data is presented to meet their specific needs. For example, users can adjust the number of records displayed per page and use the virtual column feature to calculate and display new information based on existing data.