This section describes changes to PowerCenter adapters in version 9.6.1.
PowerExchange for Salesforce
Effective in version 184.108.40.206.1, PowerExchange for Salesforce includes the following changes:
End of Life for Salesforce API Versions
PowerExchange for Salesforce does not support the following Salesforce API versions:
Previously, PowerExchange for Salesforce supported these Salesforce API versions.
The PowerCenter Integration Service writes error messages to the error log for the session.
Previously, the PowerCenter Integration Service wrote error messages to both the error log and the session log.
Java Requirements for Bulk API Target Sessions
For Bulk API target sessions, configure at least 10 to 50 MB of space for the Java temporary directory on the PowerCenter Integration Service machine.
Previously, the Bulk API did not use the Java temporary directory when writing to Salesforce targets.
Related Object Fields No Longer Available for Import
You can no longer import fields from objects related to the following Salesforce objects:
Previously, you could import fields from objects related to these objects.
Salesforce API Version
PowerExchange for Salesforce uses version 31.0 of the Salesforce API.
Use the Salesforce service URL to configure connections to Salesforce. To use the latest version of the Salesforce API, create an application connection or update the service URL in an existing application connection.
Use the following version of the Salesforce service URL:
If the new version of a Salesforce object has a different structure than the previous version of the object, re-import the Salesforce object. After you re-import the object, analyze the associated mapping to determine if you need to update the mapping.
Previously, PowerExchange for Salesforce used version 27.0 of the Salesforce API.
SOAP Request Logging
For sessions that read from Salesforce with the standard API, the PowerCenter Integration Service no longer includes SOAP requests in the session log.
Previously, you could view SOAP requests in session logs when you configured the session for verbose tracing.