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.

Test your field mapping with existing co-sells

You can test your mapping with any of your existing Salesforce opportunities or referrals before you publish your changes in Salesforce.

In Tackle > Account settings > Field mapper, select the Tackle object and the cloud marketplace you want to map.
Click Test with a Salesforce opportunity.

The Salesforce opportunities menu opens.
Search an opportunity ID, name, or keyword. Once you search, a list of results appears.
Click Select next to the opportunity you want to test. After you select, the opportunity will show as Selected.
Click the X to close the menu and return to the field mapper. You'll now see an Opportunity data column. The name of the test opportunity you selected appears at the top left.
Review and edit your mappings as needed.
When you’re done, click Publish.

Import test environment mapping into your Tackle production account

If you previously mapped Salesforce fields in your Tackle test environment, Tackle offers a convenient option to import these existing mappings directly into your Tackle production account.

Note

Once you've configured your field mapping in a test environment, the automatic import option will be available.

In Tackle, switch to your Tackle production account if you’re currently in your test environment.
In your Tackle production account, go to Account Settings > Field Mapper.
Once you’re in Field Mapper, an Import field mapper pop-up opens.
Select the test environment from where you want Tackle to import and then click Import. Tackle will start importing. If some of the mappings from your test account do not match fields in your production account, you will see a message listing the affected fields.
Review and map the fields as needed.
When you’re done mapping and are ready to publish, click Publish.
Note: Tackle will import the field mapper as a draft. You’ll need to publish to save any changes, including the imported fields.
After you publish, the import and your changes will be live and synced with Salesforce. For more on mapping your fields, see Map your Salesforce fields.

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. You can select and map one or more picklist values as needed.

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 in the field mapper: 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 @ to search and select from a list of Salesforce fields.
- Any Salesforce fields that you add will be shown using standard template markup: `{{ Opportunity.OpportunityType }}`
Note: When selecting more than one value, use dashes to search new value fields to add and separate the data.

Here's how it looks once you enter @ to use dynamic fields.

Here's an example of the standard format that would show if you were to select the following fields. As you can see, the dashes separate the values added:

Now, you'll need to add your opportunity information to map to Salesforce. You may want to reference your Salesforce Opportunity to enter the correct information. Example Opportunity in Salesforce:

Using the information from your Opportunity, enter it in the Salesforce field in the format provided. Here's the entry using the example Opportunity.

Note: The Opportunity data field (in blue below) for that AWS field will update once you enter information in the Salesforce field.

Configure contract start and end dates for your co-sells

Note

This is currently available for AWS Marketplace only.

You can standardize and automate your co-sell contract terms using configurable formulas for start and ends dates when mapping your fields.

In Tackle > Account settings > Field mapper, click the Co-Sell tab and then click the AWS tab.
Scroll to the Launch and close fields section and find the Contract start date and Contract end date AWS fields.
Go to the Salesforce field for Contract start date and click the configuration icon.

The Configuration field menu opens.
Enter information to configure the contract start date:
1. Add days (in numerical form) to the contract start date.
2. To start the contract on a weekday, click the toggle to ON. When this is enabled and the date starts on a Saturday or Sunday, Tackle will add days to begin on the next business day. To disable, click the toggle to OFF.
When you’re done, click Save.
Now go to the Salesforce field for Contract end date and click the configuration icon. The Configuration field menu opens.
Enter information to configure the contract end date:
1. Select the end date type:
  1. Use mapped Salesforce field - Tackle uses the contract end date in the mapped Salesforce field. If you select this option, you can also add days (in numerical form) to the contract end date.
  2. Contract must default to one year - Tackle sets the contract end dates to 12 months from the contract start date configured in Field Mapper. You cannot add days to the contract end date.
2. To end the contract on a weekday, click the toggle to ON. When this is enabled and the date ends on a Saturday or Sunday, Tackle will add days to end on the next business day. To disable, click the toggle to OFF.
When you’re done, click Save.
Once the contract dates are configured, you’ll see a blue dot indicator next to field(s). You can click the configuration icon to remove the configuration.

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.

In Tackle > Account settings > Field mapper > Co-Sell > AWS, go to the Amount AWS 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.

Filter AWS dimensions to show in Field Mapper

Configure your API name field to exclude dimensions from your AWS private offers that return an empty API name from your Salesforce Opportunities.

To configure and turn on filtering:

In Tackle > Account settings > Field mapper, click the Offers tab and then click the AWS tab.
Scroll to the Dimension fields section and find the API Name AWS field.
For the API name Salesforce field, click the configuration icon.
Note: Field value in the image is for reference only.

The Configuration field menu opens.
Enter information to configure:
1. API name - The API name mapped field will show here. If you need to update this field, make changes on your Field Mapper form and then return to this menu to configure the field.
2. Exclude when API name is blank - Click the toggle to ON to exclude dimensions that don’t have an API name in a Salesforce Opportunity.
When you’re done, click Save.
Once the API name Salesforce field is configured, you’ll see a blue dot indicator next to the field. You can click the configuration icon to remove the configuration.

Recommended mapping

How to use recommended mapping

To access the latest versions of recommended mapping for Tackle for Salesforce, click the link for the cloud marketplace and feature mapping you want to view (below).

When you're on the web page, click the tab for the mapping you want. The page will show recommend mapping for Co-Sell and / or Offers (Direct, Partner).

AWS Marketplace