Preview feature
This feature is currently in preview and not yet accessible to all Tackle customers. For more information, contact [email protected].
This is the third article in a series guiding you through everything you need to know to set up, support, and succeed with the Tackle for Salesforce integration.
Map your Salesforce fields (You are here)
In this article, you’ll connect the fields from Amazon Web Services Marketplace (AWS) to your corresponding fields in Salesforce in the Field mapper. Once these fields are mapped, you’ll be able to create and manage your co-sells and offers directly from Salesforce using pre-populated data from AWS.
Who should map your Salesforce fields?
We recommend this guide be completed by your Alliance Leader or someone else in your business familiar with your cloud marketplace co-sell and offers data. It also may be helpful to consult with someone with knowledge of the Salesforce data model and make a plan for which data fields in AWS you want to import into Salesforce
Before you begin
Complete the steps in our articles Tackle for Salesforce — Preparing to install and Installation guide.
If you plan on using Salesforce to create and manage co-sell opportunities, connect your Tackle account AWS for Co-Sell.
If you plan on using Salesforce to create and manage offers, connect your Tackle account to AWS for Offers.
Get permissions in your Tackle account to access the Field Mapper. If you don’t already have these permissions, ask your Tackle Administrator.
Field Mapper best practices
This article includes separate instructions to map fields for Co-Sell and Offers. While the mapping experience is different for each feature, we’ve listed some best practices that work for both. Keep these tips in mind to make your field mappings work smoothly and remain easy to use and understand.
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
You can map any cloud co-sell or offers field from AWS to any opportunity or related object field in Salesforce. To find a Salesforce field for a mapping, just start typing the field name and select it in the drop down list.
If you’re not sure what a particular cloud field is used for or what you should map it to in Salesforce, just open the tip next to the field label. We’ve included explainers for all of them.
Set default values in your required fields to prevent errors
To prevent errors if a field has empty data for an opportunity, we recommend setting default values for all required fields. You can set a default data in two different ways:
You can map a field, 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.
You can set a default value without mapping the field. In this case, Tackle will fill your 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 — you can map the values of your list in Salesforce to align to the values in the AWS field list to 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.
Define patterns with dynamic field templates
To help enforce consistency and quality across your Co-sell and Offers operations, you can 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 into the drop down and type ‘@’, then choose from a list of Salesforce fields. Any Salesforce fields that you add will be indicated using standard template markup, for example: `{{ Opportunity.OpportunityType }}`
Map your AWS Co-Sell fields in Salesforce
Sign in to Tackle. In the left menu, click Account Settings, then click the Salesforce Field Mapper tab.
Click the Co-Sell tab, then select AWS.
In the Customer Fields section, you’ll see a list of all of the co-sell fields available to you in AWS. Click the tooltip next to any field to learn more about what data that field contains.
Choose any AWS field, then click the Salesforce field drop-down menu to view a list of all fields from your Salesforce Opportunity object — including all of your objects related to the Opportunity as well as their fields. You can type the name of your field to filter down the list of values and their paths to find it quickly.
Note: Not seeing a particular field or object? Make sure that your Integration User has ‘read’ permissions on all objects and fields that you want to pull in for the Field Mapper. At a minimum, that should include the Account, Opportunity and Quote objects.
Select the Salesforce field that you want to map to your AWS field.
Tip: Open a Salesforce opportunity in another tab to use as reference while you’re mapping fields. This can be a helpful reference to make sure that you’re selecting the correct fields!
In the Type column, you’ll see the type of data that your AWS field accepts. If your field is a Picklist type, click the Picklist icon next to the Salesforce Field drop-down menu to open the picklist mapper. From here you can map each value in that field to any value in the cloud’s corresponding list.
Warning: Mapping your Closed Won and Closed Lost Stage values will trigger an automation to auto-close lost or auto-close launch any co-sells that are in that stage.
If a field accepts default values, you can enter the value you want to return if this field receives no data from AWS or has no corresponding field in Salesforce. To prevent errors, we recommend setting default values for all required fields.
The AWS Co-Sell fields Partner Project Title and Custom Business Problem accept dynamic template values in addition to standard text. To add data from a Salesforce field to the value in one of these fields, type “@” and choose a Salesforce field to populate this value. You can also enter static text along with your dynamic data.
Partner Project Title: Use templates to build a co-sell deal name that includes specifics from the deal, with standard text to add consistency at scale. This can help increase your co-sell acceptance rates.
Custom Business Problem: Build a dynamic description to explain the specific challenge or issue a company is facing within their operations that they are looking to solve by utilizing your product or service.
Continue this process until you’ve mapped all the required fields from AWS.
If you want to map optional fields from AWS as well, click Map optional customer fields. Then continue mapping each optional field that you want to track in Salesforce.
Once you are finished mapping your fields, click Publish at the bottom of the page, and your mappings will be live in the environment that you built them in (test/sandbox or production). You can also click Save as Draft to save your progress as you go if you aren’t ready to publish your mappings just yet.
Now that all your fields are mapped, it’s time to test and make sure all your data is working correctly.
Create a test AWS co-sell
Sign in to your Salesforce sandbox org and access an Opportunity you want to use for testing.
In the Tackle widget, click the Co-Sell tab, then click Co-sell with AWS.
A Tackle form titled Create a Co-Sell will appear with data from each field that you mapped in the field mapper in the Customer Details section. Take a look at each field in this section to make sure that all the data matches the field it’s contained in. If something isn’t right, go back to Tackle and use the Field Mapper to make any adjustments necessary.
If all the data looks correct, click Submit to cloud to submit your co-sell. Congratulations, you successfully created a test co-sell!
Note: Don’t worry, you’re still in a test environment — none of this is submitting data to the real cloud!
To view your co-sell in Tackle, return to your Tackle Platform and navigate to the Tackle test account you used for your field mapper, if you aren’t in that environment already. To switch environments, click on your Account in the left menu, then use the account picker to select your account.
In the left menu, click Co-Sell, then use the slider in the top-right to enable Preview the new co-sell experience.
The test co-sell you created in Salesforce will now load in your list of co-sells. Click on it to view the co-sell details and verify that all the data is mapped as you would expect.
Click Approve or Reject to test approving or rejecting your co-sell.
You can continue adjusting your Field Mapper and creating new test co-sells until everything is working exactly how you want. When you’re done with all of your field mapping, let your Salesforce Administrator know — all that’s left to do is push your integration live to production!
Map your AWS Direct Offers fields in Salesforce
Sign in to Tackle. In the left menu, click Account Settings, then click the Salesforce Field Mapper tab.
Click the Offers tab, then select AWS, then Direct.
In the Buyer Fields section, you’ll see a list of all the offers fields available to you in AWS. Click the tooltip next to any field to learn more about what data that field contains.
Choose any AWS field, then click the Salesforce field drop-down menu to view a list of all fields from your Salesforce Opportunity object — including all of your objects related to the Opportunity as well as the Opportunity fields. You can type the name of your field to filter down the list of values and find it quickly.
Note: Not seeing a particular field or object? Make sure that your Integration User has ‘read’ permissions on all objects and fields that you want to pull in for the Field Mapper. At a minimum, that should include the Account, Opportunity and Contact objects.
Select the Salesforce field that you want to map to your AWS field. Use this table for a list of all AWS fields and recommended Salesforce fields to map to each:
AWS Field | Description | Recommended Salesforce Field Mapping |
AWS Account ID | This is the AWS Account ID that your buyer will purchase your offer from. | Custom field recommended: Opportunity > Account > AWS Account Number |
Company name | The name of your buyer’s company. | Opportunity > Account > Account Name |
Salesforce object for buyer contact | Buyer contact fields (Full name, email, title) must first have a Salesforce object selected before the fields can be mapped. | Opportunity > Contact |
Full name | This is the name of the person who will accept your private offer. | Contact > Full Name |
The email for the person who will accept your private offer. You can send this email detailed purchase instructions to accept their offer. | Contact > Email | |
Title | The title for the person that will accept your private offer. | Contact > Title |
Offer name | The name for your private offer on the marketplace. | ‘Offer for ‘ Opportunity > Account > Account Name ‘ for quote ‘ Opportunity > Primary Quote > Quote Number |
Offer description | Description for your offer. This is not visible to your buyer. | ‘Offer for ‘ Opportunity > Account > Account Name ‘ and account number ’ Opportunity > Account > Account Number ‘ for quote ‘ Opportunity > Primary Quote > Quote Number |
Renewal | Indicates if this offer is for a renewal or not. Private offers for renewal receive a lowered marketplace fee rate. |
|
Renewal type | Indicates whether your renewal is for an ‘Existing customer moving to AWS marketplace’ or an ‘Existing customer on AWS marketplace’ |
|
Offer acceptance deadline | The last date that your buyer can accept your private offer. This is UTC time in AWS. | Opportunity > Target Close Date |
Payment model | Indicates if this offer will use a ‘Payment schedule’ or be paid ‘Upfront’. When using ‘Upfront’ pricing, your buyer may choose the quantity that they want for each dimension offered. |
|
Contract start | Indicates if this offer will ‘Start on acceptance’ or will be ‘Future dated’. |
|
Currency | The currency that this offer will be created in. AWS only supports certain currencies and only for certain listing types. You must have a disbursement profile configured for a currency before an offer can be created in that currency. Learn more about currency on AWS here. |
|
Offer duration | Set the duration of your agreement (in months). Applicable when 'start on acceptance' is selected as the contract start |
|
Start date | Set the date when your agreement will begin. Applicable when 'Future dated' is selected as the contract start |
|
End date | Set the date when your agreement will end. Applicable when 'Future dated' is selected as the contract start |
|
Salesforce object for payment schedule fields | Payment schedule fields (Invoice date, payment) must first have a Salesforce object selected before the fields can be mapped | Opportunity > Primary Quote > Order > Invoice > Invoice Line Item |
Invoice date | The dates on which your buyer will be invoiced by AWS for your private offer. | Invoice Line Item > Invoice Line Start Date |
Payment | The amounts that corresponds with the dates for when your buyer will be invoiced by AWS for your private offer. | Invoice Line Item > Charge Amount |
Marketplace fee | Optional: Used by Tackle in order notifications and reporting to provide you with accurate gross and net total contract value amounts. |
|
In the Type column, you’ll see the type of data that your AWS field accepts. If your field is a Picklist type, click the Picklist icon next to the Salesforce Field drop-down menu to open the picklist mapper. From here you can map each value in that field to any value in the cloud’s corresponding list.
If a field accepts default values, you can click the Default value drop-down menu and enter the value you want to return if this field receives no data from AWS or has no corresponding field in Salesforce. To prevent errors, we recommend setting default values for all required fields.
Continue this process until you’ve mapped each field from AWS that you want to include.
Once you are finished mapping your fields, click Publish at the bottom of the page, and your mappings will be live in the environment that you built them in (test/sandbox or production). You can also click Save as Draft to save your progress as you go if you aren’t ready to publish your mappings just yet.
Now that all your fields are mapped, it’s time to test and make sure all your data is working correctly.
Create a test AWS Direct Offer
Create a new listing in your AWS production account🔗 to use for your test, and set its status to either Preview or Published.
Sign in to Salesforce and access an Opportunity you want to use for testing.
In the Tackle widget, click the Offers tab, then click Create AWS Offer.
Click the radio button for a Direct offer and click New offer, then click Continue.
A Tackle form titled Create direct offer will appear with data from AWS mapped into each field. Take a look at each field in this section to make sure that all the data matches the field it’s contained in. If something isn’t right, go back to Tackle and use the Field Mapper to make any adjustments necessary.
If all the data looks correct, click Save to draft. Because this is a test environment, clicking ‘Submit to cloud’ will not function correctly. Congratulations, you successfully created a test offer!
Note: Don’t worry, you’re still in a test environment — none of this is submitting data to the real cloud!
You can continue adjusting your Field Mapper and creating new test offers until everything is working exactly like you want. When you’re done with all your field mapping, let your Salesforce Administrator know — all that’s left to do is push your Tackle - Salesforce integration live to production!