The field mapping experience can be different for Co-Sell and Offers, but you can use best practices that work for both. Here are general practices and recommended mapping to keep in mind as part of getting started. Once you're ready, start mapping your Salesforce fields in Tackle.

General mapping practices

Test your work before going live

We recommend you configure the field mapper in your test environment first. Then create a test co-sell and/or offer after you publish your mappings to verify that all the fields you mapped have accurate opportunity data and auto-fill as you expect before you push these updates to production.

Map as many fields as you want

Map any cloud Co-Sell or Offers field from AWS or Microsoft to any opportunity or related object field in Salesforce. To find a Salesforce field for a mapping, you can type the field name and select it in the dropdown list.

Unsure what a field is for or what you should map it to in Salesforce? Click the tip icon next to the field label to learn more.

Set default values in your required fields to prevent errors

To prevent errors if a field has empty data for an opportunity, set default values for all required fields. You can set a default data in two ways:

Map a field and then set a default value. In this case, Tackle will use the default value as a fallback if no data is found in your mapped field.
Set a default value without mapping the field. In this case, Tackle will fill the field with the default value every time.

Use list mapping for your picklist and multipicklist fields

For picklist fields that can only accept certain pre-defined values, such as Country, Industry, or Stage, map the values of your list in Salesforce to align to the values in the AWS field list and help make your data match.

Any time you select a field in Salesforce that is either a picklist or multipicklist, click the list mapping icon to the right of your Salesforce field to open list mapping.

From here you can map each value in that field to any value in the cloud’s corresponding list.

Calculate your estimated monthly recurring revenue

Note

This is currently available for AWS Marketplace only.

If your organization reports on revenue through annual recurring revenue or total contract value, you can adjust the Amount field for AWS co-sell to calculate it to a monthly breakdown.

To calculate:

In Tackle > Account settings > Field mapper > Co-Sell > AWS, go to the Amount field and click the fx icon.

The Configure formula menu opens
Map your fields that host the amount and contract length. Optionally, add the consumption rate.
When you’re done, click Save.

Now whenever you create an AWS co-sell, it will be in the context of monthly recurring revenue.

Define patterns with dynamic field templates

To help enforce consistency and quality across your co-sell and offers operations, build a template that includes both static text and dynamic data from one or more Salesforce fields.

This feature is limited to specific co-sell and offers fields. Some examples include Co-Sell Partner Project Title, Customer Business Problem, and Offer Name.

To add plain text, type it out.
To add a dynamic value from a Salesforce field to your template, click the dropdown and type @, and then select from a list of Salesforce fields. Any Salesforce fields that you add will be shown using standard template markup: `{{ Opportunity.OpportunityType }}`

Automate the creation of your co-sells and offers by mapping your Salesforce fields to any cloud-specific fields.

Recommended mapping

How to use recommended mapping

To access the latest versions of recommended mapping, click the link for cloud marketplace you want to view (below). The page will include recommendations for Co-Sell and/or Offers (Direct, Partner). When you're on the web page, click the tab for the fields you want to view.

AWS Marketplace