Labra Salesforce Mapping Manager Guide (Native App)

Table of Contents:

• Prerequisites
   
• Overview
   
• Mapping for Co-sell (Labra referral)
   
  • AWS Cloud Mapping for Co-sell (Labra referral)
     
  • Microsoft Cloud Mapping for Co-sell (Labra referral)
     
• Mapping for Marketplace Private Offers (Labra offers)
   
  • AWS Cloud Mapping for Marketplace (Labra offer)
     
  • Microsoft Private Offer Mapping Manager (Labra offer)
     
  • GCP Private Offer Mapping Manager (Labra offer)
     
• AWS Resale Authorization Mapping

✅ Prerequisites

Before configuring the Labra Salesforce Mapping Manager, make sure you’ve completed the following:

1. Complete the onboarding prerequisites for each applicable cloud provider:
    
   • AWS onboarding prerequisites
   • Microsoft onboarding prerequisites
   • GCP onboarding prerequisites
      
2. Sign in to app.labra.io.
    
3. Connect Labra for Co-sell Cloud Settings for each applicable cloud provider.
    
4. Install the Labra Salesforce App.
    
5. Connect Salesforce to Labra.
    
6. Set up the Labra Salesforce App.

🗺️  Overview

The Labra Mapping Manager is a Salesforce application that lets you control how information from your Salesforce records is mapped to Labra fields.

By configuring these mappings, you can automatically populate information when creating:

• Co-sell referrals
• Marketplace offers
• AWS Resale Authorizations

Instead of entering the same information manually each time, you can map Labra fields to existing Salesforce fields or define a default value.

Fig. 1

⚙️  How the Labra Mapping Manager works

When you open the Mapping Manager, you'll see a table with the following columns:

• Referral/Offer Field: The Labra field that can be populated.
   
• Salesforce Field: The Salesforce Opportunity, Account, or User field that should provide the value.
   
• Default Value: A fixed value to use instead of a Salesforce field.
   
• Hidden: Hides the field when creating the referral, offer, or resale authorization while still applying the mapped value.
   
• Read-only: Displays the mapped value but prevents users from editing it during creation.

✨  Additional features

The Mapping Manager also includes the following options:

• Filter: Filter fields by status, including mapped, required, unmapped, or optional.
   
• Refresh Referral Fields: Refreshes the available referral fields based on Salesforce metadata and page layout.
   
• Refresh Offer Fields: Refreshes the available Marketplace offer fields.
   
• Refresh Resale Fields: Refreshes the available Resale Authorization fields.

🛠️  How to Access the Labra Mapping Manager

To open the Mapping Manager:

1. Open the App Launcher in Salesforce.
2. Search for Labra Mapping Manager.
   
   
   Fig. 2
    
3. Open the application.

🔗  Mapping for Co-sell

The Mapping Manager supports co-sell field mapping for AWS and Microsoft.

AWS Cloud Mapping for Co-sell (Labra referral)

After opening the Mapping Manager:

1. Select the AWS cloud.
2. Click Refresh Referral Fields to load the AWS-specific referral fields.
   
   
   Fig. 3
    
3. For each field, choose either:
   • A Salesforce Field to populate the value dynamically, or
   • A Default Value to use a predefined value.
4. Click Save when you're finished.
   
   
   Fig. 4

Mapping AWS Products and Solutions (Labra referral)

Before mapping AWS products or solutions, make sure you are fully onboarded to Labra for Co-sell and have an active connection.

Once the connection is active:

1. Map your AWS solutions or products as needed.
2. Click Save.
   
   
   Fig. 5
    

Microsoft Cloud Mapping for Co-sell (Labra referral)

To configure Microsoft mappings:

1. Select Microsoft under the cloud marketplace options.
2. Microsoft-specific fields will appear in the Mapping Manager.
   
   
   Fig. 6
    
3. Map each field to a Salesforce Field or provide a Default Value.
4. Click Save.
   
   
   Fig. 7

You can also configure Microsoft solutions from the Solutions tab. Select the appropriate solution from the dropdown and click Save to add the default solution.

🛒  Mapping for Marketplace Private Offers (Labra offers)

The Mapping Manager supports Marketplace offer mappings for AWS, Microsoft and GCP.

AWS Cloud Mapping for Marketplace (Labra offer)

Select the AWS marketplace option to configure AWS offer mappings.


Fig. 8

AWS Private Offer Fields (Labra offer)

You can map AWS offer fields to Salesforce fields or configure default values.

Available fields include:

• Company Name
• Contract Duration
• Entitlement Option
• Custom Email Message
• AWS Account ID
• EULA Type
• Internal Notes
• Offer Expiration Date
• Offer Name
• Renewal Type
• Subscription Start Date
• Subscription End Date

Each field includes Read-only and Hidden options:

Read-only

When Read-only is selected, the mapped value is displayed when creating the AWS offer but cannot be edited.

Hidden

When Hidden is selected, the field is not displayed when creating the AWS offer. The mapped value is still applied and can be viewed after the offer is saved.

The following fields also support the Hidden option:

• Custom Metadata
• Global Metadata
• Stakeholders

Dimensions

Use the Dimensions section to configure mappings for product dimensions.

You can map dimensions to Salesforce fields or provide default values. Dimensions can also be configured as Hidden or Read-only.


Fig. 9

EULA

The EULA tab allows you to configure how EULAs are applied when creating AWS offers.

Default EULA

You can select a default EULA file that will automatically be applied when creating an AWS offer.

Select the file and click Save.


Fig. 10

Mapping-based EULA

You can also configure EULAs based on a Salesforce object.

To create a mapping:

1. Select the object that defines the EULA mapping.
2. Click Add New EULA Mapping.
3. Enter the required Key and Document ID.
4. Click Save.
   
   
   Fig. 11

You can add multiple EULA mappings.

When an AWS offer is created, the appropriate EULA is selected automatically based on the configured key and document ID.

Default + Mapping-based EULAs

You can configure both a default EULA and mapping-based EULAs. When both are configured, both EULA files will be uploaded when the AWS offer is created.


Fig. 12

Fig. 13

Recipient Source

The Recipient Source tab determines where recipients are pulled from when creating an AWS offer.


Fig. 14
 

There are three options:

Contact

Recipients are retrieved from the contacts associated with the account linked to the opportunity.

Contact Roles

Recipients are retrieved from the contacts associated with the opportunity.

Contact Roles is selected by default.

Other

Select Other to choose a Salesforce object and map the recipient field to a field on that object.


Fig. 15

After configuring the mapping, click Save.

Microsoft Private Offer Mapping Manager (Labra offer)

Fields

You can map Microsoft offer fields to Salesforce fields or configure default values.


Fig. 16

Available fields include:

• Company Name
• Custom Email Message
• Microsoft Billing ID
• Internal Notes
• Offer Expiration Date
• Offer Name
• Specified Month
• Specified End Date
• Subscription Start Date

Each field includes Read-only and Hidden options.

• Read-only: Displays the mapped value but prevents users from editing it when creating the offer.
• Hidden: Hides the field when creating the offer while still applying the mapped value.

The following fields also support the Hidden option:

• Custom Metadata
• Global Metadata
• Stakeholders

GCP Private Offer Mapping Manager (Labra offer)

Fields

You can map GCP offer fields to Salesforce fields or configure default values.


Fig. 17

Available fields include:

• Company Name
• Custom Email Message
• GCP Account ID
• Internal Notes
• Offer Expiration Date
• Offer Name

Each field includes Read-only and Hidden options.

• Read-only: Displays the mapped value but prevents users from editing it when creating the offer.
• Hidden: Hides the field when creating the offer while still applying the mapped value.

The following fields also support the Hidden option:

• Custom Metadata
• Global Metadata
• Stakeholders

AWS Resale Authorization Mapping

The AWS Resale Authorization section includes the following tabs:

• Fields
• Dimensions
• Reseller Agreement
• EULA for Buyers
• Installments
• Global Metadata
• Recipient Source

Configured values are automatically pre-populated when creating an AWS Resale Authorization.

Fields

You can map Labra Resale Authorization fields to Salesforce fields or provide default values.

Fig. 18

Available fields include:

• Authorization Name
• Authorization Description
• Authorization Time Length
• Buyer Account ID
• Company Name
• Contract Duration
• Custom Email Message
• Discount Type
• Duration (in months)
• End Date
• EULA for Buyer
• Internal Notes
• Maximum Allowed Start Date
• Percentage Discount
• Renewal Type
• Reseller Agreement
• Reseller AWS Account ID

The following fields also support the Hidden option:

• Custom Metadata
• Global Metadata
• Stakeholders

When a field is hidden, it will not appear while creating the Resale Authorization, but the configured value will still be applied.

Dimensions

You can map product dimensions to Salesforce fields or provide default values.

Fig. 20
 

When Flexible Payment Schedule (FPS) is selected while creating a Resale Authorization, mapped dimension values are automatically populated as quantities.

You can also use Read-only or Hidden to control how dimension fields appear during creation.

Fig. 21

Additional Mapping Options

The Reseller Agreement, EULA for Buyers, Global Metadata, and Recipient Source options work similarly to their corresponding Marketplace Offer settings.

Installments

The Installments tab allows you to select a Salesforce object and map installment fields to Salesforce fields.


Fig. 22
 

Fig. 23

After configuring the mappings, click Save.