Product mapping allows you to define which fields from the product (OpportunityLineItem) to be sent to Oneflow when creating a contract. This feature is flexible enough to work with quantities, checkboxes, or single choices in Oneflow contracts. Also, it is possible to define fields that Salesforce will update once a contract is signed.
Configure product mapping
To configure product mapping in Salesforce:
- Navigate to Setup > Custom Settings > Oneflow Product Mapping > Manage > Product Mapping and click Edit.
- Here you can change the product mapping configuration to use Salesforce fields that suit your company best:
- Name - product name shown in Oneflow.
- Description - product description shown in Oneflow.
- Price1 - product Price1 shown in Oneflow.
- discount1 - product Discount1 shown in Oneflow.
- Price2 - product Price2 shown in Oneflow.
- discount2 - product Discount2 shown in Oneflow.
- quantity - product quantity shown in Oneflow.
- quantity_type - product Quantity Type shown in Oneflow.
- default_quantity_type - product Default Quantity Type shown in Oneflow. Choose between number, checkbox, or single-choice.
- Customer_selection - a field that is updated when the contract is signed.
Example
Below is an example of the out-of-the-box product mapping settings:
- Name: PricebookEntry.Name
Product name comes from OpportunityLineItem > PricebookEntry > Name. - Description: Product2.Description
Product description comes from OpportunityLineItem > Product2 > Description. - Price1: UnitPrice
Product Price1 comes from OpportunityLineItem > UnitPrice. - discount1: Discount
Product Discount1 shown in Oneflow. - Price2: Optional
- discount2: Optional
- quantity: Quantity
Product quantity comes from OpportunityLineItem > Quantity. - quantity_type: Optional
- default_quantity_type: Optional
The default option for product Quantity Type is Number. - Customer_selection: Optional.
As shown in the configuration above, it is possible to use fields from the OpportunityLineItem itself or fields from other objects related to the OpportunityLineItem (like the Product Name shown in the contract is coming from the Name field from PricebookEntry related to this OpportunityLineItem.)
Advanced configuration
Oneflow product table allows you to work with quantities, checkboxes, or single-choice selections.
Let's consider different scenarios and how to configure them
Number
When creating a contract, you want to display a product's quantity.
Checkboxes
When creating a contract, you would like to allow product selection using a checkbox for a product.
To use checkboxes in product mapping settings, change Oneflow Default Quantity Type to the checkbox.
Single choice
When creating a contract, you would like to allow product selection for only one product.
To use a single choice, change Oneflow Default Quantity Type to Exclusive in product mapping settings.
Default Quantity Type vs. Product Quantity Type
Product QuantityType takes a field from a product and shows that product in the Oneflow contract accordingly.
The Product field for this purpose must be a text or a dropdown field with values number, checkbox, or exclusive.
Note:
If Product Quantity Type is set, then it takes precedence over Default Quantity Type, i.e., the value for Default Quantity Type is ignored.
When the Product Quantity Type is not mapped or it might be mapped but not set for a specific product, then the Product Type falls back to the Default Quantity Type.
This mapping is beneficial for creating contracts where you want both Product Selection and Product Quantity. For example,
2-way sync for products
When a contract gets signed, it's possible to sync the product selection back to Salesforce. This is useful for tracking the products the customer signed up for. For example, syncing back the number of licenses a customer has bought or any other extras they might be interested in.
To enable 2-way sync for products, you must fill in the Product Customer Selection in Product Mapping with a field (editable) from OpportunityLineItem.
For example, check our video, where we are syncing back the quantity of the products to Salesforce after a contract is signed.
Here is another example of where we are syncing back the customer's selection of the products.
Limitations
Oneflow product table
The following features are not supported:
- Product Reorder
- Product Renaming
- Adding/Removing Products
Salesforce opportunity products
The following features are not supported:
- Product Reorder
- Product Renaming
- Adding/Removing Products
Any of the above changes will require creating a new contract; the existing contracts will not be updated.
Note: Product name is mandatory in product mapping.