Salesforce Features
AppExchange API 7.0
With the Winter ’06 release, salesforce.com is upgrading the
AppExchange API (previously known as the Sforce Web services API). As
always, considerable effort has been made to ensure backward
compatibility for applications that have been written against previous
versions of the SOAP API, starting with API 2.5. (Note: older XML-RPC
APIs should remain unchanged with this release.) The new AppExchange
API 7.0 provides a number of powerful enhancements that further improve
any integration already in place between Salesforce and your other
systems.
This feature is available in Enterprise and Unlimited Edition.
Tools and Resources
Feature Details
- Upsert Call: The 7.0 API has a new call: upsert. This powerful new call allows integrations to match on a custom field and either create or update based on the presence of an existing record. Use this feature when integrating with a back-end accounting or ERP system or to prevent duplicate records.
- System Fields: When migrating data from an external system, the 7.0 API lets customers set the CreatedBy, CreatedDate, LastUpdateBy, and LastUpdateDate fields, as well as a number of other fields that were previously read-only. To enable this feature, contact salesforce.com support.
- Office Toolkit: The Office toolkit enables Microsoft Office developers to utilize the power of the AppExchange API (all API versions). With Winter ’06, documentation is being provided for the Office toolkit, as well as a distributable MSI file.
- Improved Performance: The API SOAP stack has been re-architected from the ground up to have improved performance.
- Create and update operations will not update the Most Recently Used (MRU) list by default in the 7.0 API. A new header will allow developers to update the MRU for those that need to maintain backwards compatibility (note that the behavior for API 6.0 and below will not change). Skipping MRU updates can improve performance of bulk loads as much as 25 percent.
0 Comments