You are here: Integrating With CPQ Cloud > Integration Guides > Salesforce Integration

Salesforce Integration

OVERVIEW

There are several ways to integrate CPQ Cloud with Salesforce.

CPQ Cloud will no longer release updates to Salesforce integration Managed Packages prior to v5.0. With the release of 2015 R2, only Managed Packages v5.x and v6.x are officially supported.

Although Salesforce integrations that use a Managed Package prior to v5.0 are still expected to function, new issues that arise in these versions will not be addressed by CPQ Cloud.

For information on previous releases of the Managed Package, see the Salesforce Integration Guides in My Oracle Support.

Administration Without a Managed Package

ClosedMapping an Attribute to a Salesforce Field

There are several steps to map an attribute to a Salesforce field.

ClosedWithin Salesforce

Create a new Opportunity field for the information to display:

  1. Navigate from: Setup > Customize > Opportunities > Fields.
  2. Click New.

Be aware of the variable's API name (on the Opportunity Fields page).

ClosedWithin CPQ Cloud

Locate the integration function that exports to Salesforce:


ClosedDetermining the Salesforce Integration Version

In Salesforce, how do I identify which integration version a site is using?

Version 1:

Version 2:

Version 3:

Version 4:


TROUBLESHOOTING

Common Questions

ClosedUsing the Salesforce Debug Logs

  1. Locate a Quote that has an issue.
  2. Turn the Debug Logs on in Salesforce.
    1. Navigate from: Setup > Monitoring > Debug Logs > “New” button.
    2. Add it for the user you are logged in and/or the user that is performing the Saves to Salesforce.
  3. Attempt to save the Quote that is causing the issue.
  4. Return to the Debug Logs and look for any logs that are listed as a “Failure” in the Status column.

ClosedWhy can't I map the Quote Field to the Opportunity Field?

The Field may be set as a Date/Time type. Change the Field to String type.

ClosedSave and Synch action failed

This occurs when attempting to communicate with a partner site. When the action fails, the following error message appears: "sObject type 'BIGM_Quote__c' is not supported. If you are attempting to use a custom object, be sure to append the '__c' after the entity name. Please reference your WSDL or the describe call for the appropriate names."

Solution: Update the CPQ Cloud custom quote object and update the field name to BIGM_Quote.

ClosedOpen Quote action failed

This occurs when attempting to communicate with a partner site. When the action fails, the following error message appears: No such column 'BIGM_Primary__c' on entity 'BIGM_Quote__c'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names."

Solution: Update the primary field name to BIGM_Primary.

ClosedMultiple instances of a single Quote are appearing in Salesforce

Solution: When saving with Salesforce, ensure that the necessary Integration XSLs are located on the action that is being performed.

ClosedExtra line item added to Opportunity Products section when a Primary Quote is Save & Synced

Problem: An extra line item is added to the Salesforce Opportunity Products section after performing a Save & Sync to a quote recently set as primary. The rows appear inaccurately; a part may have another line item's list price and/or sales price. The problem is that there are no Salesforce Parts for the CPQ Cloud Models. When CPQ Cloud passes the XML to Salesforce, the model is treated as a line item.

Solution:

  1. Update the Save and Sync and Set as Primary Quote Advanced Modification Rules.
  2. When looping through the line items, add an argument to the "If" statement to ensure that the line item is model or part line item. For example:

    if ( line.sfLineItemId_line == "" AND not(line.optional_line) AND len(line.sfPricebookEntryId_line) > 1) {

ClosedSelecting "New from Primary" after cloning a Salesforce Opportunity failed

Problem: The following error messages display after a user attempts to select "New from Primary" after cloning a Salesforce Opportunity:

Could not copy transaction.

CmBsData(-1) could not be found.

Solution: Ensure that the CPQ Cloud Primary Quote attribute is located on the Opportunity. The ID stored in this attribute is used to create a copy.

ClosedUnable to clone a Quote

The inability to clone a Quote could be due to several factors. Look at the error messages to determine the cause:

Common Error Messages

ClosedInvalid cross reference id.

Solution: Ensure all parts actually exist in Salesforce and that the corresponding CPQ Cloud Parts are using the correct part IDs.

ClosedPartner Login Error for user (xxxx). An error occurred while communicating with the partner server at xxxx. This may have been due to invalid SOAP SXML generated by the XSL file.

Problem: This occurs when users attempt to sync their Partner login.

Solution: Ensure that users are using CTRL+V to paste their Security Token rather than using "right-click" paste.

ClosedError in creating process: CmIntegration(id = 4129009) could not be found.

Problem: The following error message is received after New Quote is selected in Salesforce.

Solution: Ensure that the Account Integration XSL has been created and is mapped to the _auto_refresh button.

ClosedCmVersion(process_id = -1) could not be found.

Problem: The following error message is received after Edit is selected in Salesforce.

Solution: Ensure that the process_id is being passed to CPQ Cloud. The URL parameter is bm_cm_process_id.

ClosedsObject type 'sObject' is not supported. If you are attempting to use a custom object, be sure to append the '__c' after the entity name. Please reference your WSDL or the describe call for the appropriate names.

Solution: Ensure that the Export call is being made with a sObject in it.

ClosedNo such column 'BIGM_Old_Opportunity_Id__c' on entity 'Opportunity'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.

This error occurs when attempting to communicate with a partner site.

Solution: Update the CPQ Cloud Custom Opportunity field. The Field Name should be BIGM_Old_Opportunity_Id.

ClosedNo such column 'AccountNumber' on entity 'Account'. If you are attempting to use a custom field, be sure to append the __c after the custom field name. Please reference your WSDL or the describe call for the appropriate names.

Check the import account query and import contact query files. The query string references several attributes that may not exist in the Salesforce account. The above error message occurs when these attributes do not exist and you are attempting to communicate with a partner site. Solution:

  1. Remove the attribute name from the appropriate query XSL file.
  2. Add the attribute into the Salesforce account.

ClosedCould not perform Action: Return to Opportunity

Problem: The Quote and the Opportunity were unable to be synced because at least one Product did not have a corresponding Price Book entry in the Opportunity's Price Book.

Solution: Manually add the Price Book entry in Salesforce or contact a CPQ Cloud admin in order to run a Parts Sync. Ensure that the Model parent line item is either:

Salesforce Integration Version 3 Issues

ClosedpromotePrimaryProdToOppty: execution of AfterUpdate

Problem: This occurs because BigMachinesQuoting.QuoteSyncException could not sync the Quote with the Opportunity. Price Book entries for all the products in the correct currency could not be found.

Solution: Ensure all products have a price in the Quote's currency.

ClosedSalesforce hover box refreshes with a new page after selecting an action

Solution: Ensure your action JavaScript Redirect is working with window.parent.location.hrefNOTwindow.location.

ClosedSelecting Salesforce hover box "Set as Primary" action takes you to an empty page

Solution: Revise the action JavaScript so the user returns to the Opportunity page using the following code rather than using window.location.

var targetURL = "/" + oppid;

NOTES

    As of release 2014 R1, if a customer that is configured for multi-currency and is integrated with Salesforce (using Oracle CPQ Cloud as the Parts Master) wishes to use the Delta Parts Export functionality, the Price Book entry Results Parser XSL must be modified. Ensure that the value for Salesforce parameter “Success” is equal to “True” when creating and editing Partner Price Book ID fields.

RELATED TOPICS

Related Topics Link IconSee Also