Differences

This shows you the differences between two versions of the page.

adminhelp:crmintegrationsetup:general [2011/04/21 16:25]
aquandt created
adminhelp:crmintegrationsetup:general [2011/07/11 10:47] (current)
aquandt
Line 36: Line 36:
  
 **When editing quotes from CRM opportunity, optimize saving of customer roles** - As a way to improve performance when editing quotes from CRM opportunities, logic has been introduced that will control whether customers are saved or not depending on values that are mapped from CRM. If there are no values inserted customer roles, CPQ will not save customer roles and thus save time when editing quotes from CRM. This application parameter is turned off by default and needs to be set to “TRUE” in order to turn on the optimization. \\ **When editing quotes from CRM opportunity, optimize saving of customer roles** - As a way to improve performance when editing quotes from CRM opportunities, logic has been introduced that will control whether customers are saved or not depending on values that are mapped from CRM. If there are no values inserted customer roles, CPQ will not save customer roles and thus save time when editing quotes from CRM. This application parameter is turned off by default and needs to be set to “TRUE” in order to turn on the optimization. \\
 +
 +**Performance** - As a way to improve performance when users arrive from Salesforce, there is a flag that can be checked - 'Implement Caching for Salesforce Object Definitions'. When this flag is turned on, for each user that arrives from SF, object definitions (field names, field types, permissions etc.) will be stored in CPQ database. This can improve performance when there is large number of fields (more than 100) on objects opportunity, account and contact, since CPQ queries Salesforce API for object definitions upon user's arrival and it takes 2-3 seconds for SF API to return each object definition with so many fields.
 +It's important to know that there is ability to **Refresh cache for Salesforce object definitions**. This should be done when new field is added in Salesforce to object definitions or when permissions have been changed over object fields in SF. If object fields or permissions have been changed in Salesforce and these fields are used in integration with CPQ, errors may be appear in certain integration points e.g. 'Create/Update Opportunity'.  \\
  
  
      
You are here: SAP CPQ Online HelpAdmin Page HelpCRM Integration SetupGeneral