Skip to content

Connect Salesforce ​

Salesforce joins HubSpot and Zoho as a CRM you can connect. Once connected, your Salesforce opportunities show as deals, and linked deals sync with Partner Central.

After you connect, a tenant admin adds the AWS fields to Salesforce with one click. If your Salesforce does not allow that, a Salesforce admin installs the field pack instead.

Why the fields are needed ​

CloudSmart writes each Partner Central opportunity ID onto the matching Salesforce deal so the two stay linked, in the AWS_Opportunity_Id__c field. The other AWS fields hold the Partner Central data: ACE stage, AWS stage, engagement and quality scores, next steps, your AWS rep and PDM, and the review status.

Without AWS_Opportunity_Id__c, deals cannot keep their Partner Central ID and Push to CRM does not work. Until an AWS field exists, CloudSmart skips it and everything else keeps syncing.

Requirements ​

To connect from CloudSmart: a Salesforce user whose profile has:

  • API Enabled. Most Enterprise edition profiles have it. Without it, Salesforce refuses the connection.
  • Read/write on Opportunities, and read on Accounts and Contacts. Sync acts as this user, so CloudSmart sees what this user sees.

To add the AWS fields in one click: the same user also needs Modify Metadata Through Metadata API Functions or Modify All Data. Without it, use the field pack.

For the org:

  • Enterprise edition or above. Professional edition has no API access without a paid Salesforce add-on.
  • Users must be allowed to authorize connected apps (the Salesforce default). If your org restricts this, an admin approves the CloudSmart app once under Connected Apps OAuth Usage.

Connect in CloudSmart ​

A tenant admin opens Accounts & Setup → Integrations → CRM connections, chooses + Add CRM and picks Salesforce. Sign in to your Salesforce org and approve access. Your opportunities show as deals. Turn on Sync on the row to keep linked deals up to date.

Add the AWS fields ​

On the Salesforce row, choose Add AWS fields. CloudSmart:

  • creates the 11 AWS fields on Opportunity, including AWS_Opportunity_Id__c,
  • adds two permission sets: CloudSmart AWS Partner Central (read and edit) and CloudSmart AWS Partner Central (read only), for your team,
  • assigns CloudSmart AWS Partner Central to the connected user.

When the fields exist but the connected user cannot see them, the row shows Fix field access instead.

Choosing Add AWS fields again resets both permission sets.

If the row shows "The connected Salesforce user can't add fields.", use the field pack.

Let your team see the fields ​

  1. Assign CloudSmart AWS Partner Central (read only) to the users who should see the fields. CloudSmart overwrites the fields from Partner Central, so keep them read only for everyone but the connected user.
  2. Add the fields to your Opportunity page layout.

Deleted fields ​

Salesforce keeps a deleted field for 15 days with _del in its name. You can reuse the field names right away.

Field pack ​

Use the field pack when the connected user is not allowed to add fields. It holds the 11 fields and the two permission sets.

  1. On the Salesforce row, choose Download field pack. You get cloudsmart-salesforce-field-pack.zip, a Salesforce metadata package with package.xml at its root. If a field already exists, the pack updates it.
  2. A Salesforce admin installs it one of three ways:
    • Salesforce CLI: unzip into a folder (for example field-pack), then run sf project deploy start --metadata-dir field-pack --target-org <your-org-alias>.
    • Workbench: in Workbench open Migration → Deploy, select the zip, tick Single Package and deploy.
    • By hand: in Object Manager → Opportunity → Fields & Relationships, create each field listed in the pack's package.xml with the same API name and type.
  3. Assign the permission set to the connected user.
  4. Choose Refresh in CloudSmart.

Install on the row links to this section.

Assign the permission set ​

  1. In Salesforce Setup, open Permission Sets and choose CloudSmart AWS Partner Central.
  2. Choose Manage Assignments, then Add Assignment.
  3. Select the user CloudSmart connects as and choose Assign.

If you added the fields by hand, give that user Edit on all 11 fields through field-level security instead.

To let your team see the fields, see Let your team see the fields.

Add the AWS_Opportunity_Id__c field ​

To add only the ID field by hand:

  1. In Salesforce Setup, open Object Manager and then Opportunity.

  2. Choose Fields & Relationships, then New.

  3. Select Text and continue.

  4. Enter:

    • Field Label: AWS Opportunity Id
    • Length: 255
    • Field Name: keep the filled-in AWS_Opportunity_Id
    • External ID: tick it, so CloudSmart can match deals by this ID
    • Unique: optional, recommended (one deal per opportunity)

    Salesforce adds __c, so the API name is AWS_Opportunity_Id__c.

  5. Give the connected user access in field-level security and choose Save.

CloudSmart finds the field the next time you refresh, connect or export.

Fields your Salesforce requires ​

Some orgs make custom Opportunity fields required, for example a Mode of Purchase picklist. New deal and Push to CRM cannot create a deal until those fields have a value. The Salesforce row then shows "Salesforce requires N fields on new deals."

A tenant admin chooses Set values, picks a value for each field from your org's picklist and saves. The values apply only to deals CloudSmart creates. Fields CloudSmart already fills (Name, Stage, Close Date, Amount and the opportunity ID) cannot be set here.

Good to know ​

  • Keep the connection alive. In your Connected App, set the refresh token policy to valid until revoked. If the session expires, the row shows Expired. Choose Reconnect.
  • Which orgs. Connect at login.salesforce.com. Salesforce sandbox orgs (test.salesforce.com) are not supported yet.
  • Stages. Your Salesforce owns the deal's stage. To move it when the ACE stage changes, set a stage mapping.
  • Your data stays yours. CloudSmart only reads and writes the fields shown in your deals. Field-level security stays under your control.