CR | Description |
|---|---|
ICS-4040 | Due to a Salesforce limitation, when you use an SOQL query as a Salesforce source, parent field values do not display correctly in Data Preview if there are parent-child relationships in the data set. |
ICS-4037 | Due to a Salesforce limitation, SOQL does not support aliases for JOIN queries. |
CR | Description |
|---|---|
ICS-3347 | The ability to specify the location of error files for Salesforce connections has been removed. In existing Mapping Configuration tasks that use Salesforce connections, error files are created in the default location even when a custom location was specified. |
ICS-5146 (formerly INFA 394600) | Tasks that include more than two Salesforce source objects and an SOQL query or advanced filter can fail when the query does not include the primary source object in the expression. Workaround: For an SOQL query, include the relationship path to the primary source object as follows: <relationship_path>.field_name='value'. For example, the following expression filters Salesforce data in the contact and account objects by a user named Lee: Contact.Account.CreatedBy.Name='Lee'. |
ICS-4614 | If you use Salesforce connection with Salesforce API version 34, a task fails when you select a lookup operator other than equal to (=). |
ICS-4474 | When you use version 33 of Salesforce API and select Lead or Case object as target in a Data Synchronization task, the task takes time to go to the Schedule page from the Field Mapping page. |
ICS-3004 | When you create a Data Synchronization task that uses multiple sources with a Salesforce V33 connection, you might receive an error when you add a related object before the data preview loads. Workaround: Wait until the data preview loads before you add a related object. |
CON-4195 | For Data Replication and Data Synchronization tasks that use Salesforce API version 32 or above, the Standard and Verbose execution modes provide same logging information. |
CON-1753 | When you enable the Set to Null property for checkbox fields, the NULL values for checkboxes are treated as false if the API version of the Salesforce connection that you use is version 32 or above. |
CON-1151 | When you run a Data Synchronization task by using Salesforce connection and enable the Primary Key Chunking and Row Limit options, the task fails. |
CON-1059 | When you create a saved query by using Salesforce connection, the agent fails to fetch metadata for the Geolocation field. If you create a Data Synchronization task by using this saved query, the task fails to fetch the Geolocation information. Workaround: You can use Longitude and Latitude field instead of Geolocation field. |
CON-589 | When you create a mapping with a Salesforce lookup object and select Report error option for Multiple Matches field, the Lookup transformation returns incorrect data. |
CON-562 | For a Salesforce connection, if you create a saved query using the "WITH" key word, an error message appears that says the query is not valid. Workaround: Create a saved query without the "WITH" key word. |
ICS-5171 (formerly INFA 280097) | For Data Synchronization tasks running in real time after receiving a Salesforce outbound message, Secure Agent or network connection problems can result in data loss or unexpected job behavior. |
INFA 263125 | PowerCenter tasks that write to Salesforce targets using the Salesforce Bulk API fail when run by a Secure Agent that uses FreeProxy or ISA Proxy. Workaround: If possible, use a different Secure Agent to run the task, or configure the Secure Agent to use a different proxy server. |
CR | Description |
|---|---|
INFA395101 ICS-304 | In tasks and the Mapping Designer, objects that cannot be queried by version 31 of the Salesforce API do not show up in the list of available objects for sources or targets. |
INFA 392744 | Data Replication and Data Synchronization tasks that use the Salesforce Bulk API and version 31 of the Salesforce API to replicate the following Salesforce objects fail: AcceptedEventRelation, CaseStatus, ContractStatus, DeclinedEventRelation, LeadStatus, OpportunityStage, PartnerRole, RecentlyViewed, SolutionStatus, TaskPriority, TaskStatus UndecidedEventRelation, UserProfile, and Attachment with binary fields. The tasks fail with the following error: Entity '<ObjectName>'is not supported by the Bulk API. For more information on the objects that cannot be queried with the Salesforce Bulk API, contact Salesforce. |
CTDM-279 | Due to a Salesforce limitation, the upsert operation in a Data Masking task fails when there are objects with fields that you cannot update. Workaround: Ignore the error rows and warning that you view in the task activity logs. |
INFA390073 | Due to a Salesforce limitation, the Data Masking task fails when the SOQL exceeds 20,000 characters. Workaround: Contact Salesforce to increase the SOQL character limit for the account. |
INFA389610 | Due to a Salesforce limitation, the Data Masking task with the upsert operation fails when the external ID or custom field for lookup does not exist or cannot be created in the targets. |
CON-4289 | For Data Replication and Data Synchronization tasks that use up to version 31 of the Salesforce API, the session log response is displayed in the XML format. |
CON-4288 | For Data Replication and Data Synchronization tasks that use Salesforce API version 32 or above, the HTTP request message is not included in the session log. |
CON-3224 | Due to a Salesforce limitation, the tasks with SOQL query with BULK API fail. Workaround: Use Standard API in place of BULK API. |
CON-1891 | Due to Salesforce limitation, CollaborationGroup and Group objects have the same labels even though the technical names are different. When you use a Salesforce connection with Salesforce API version 32 and above and select Display technical names instead of labels option for a Group object, the object name changes to CollaborationGroup if the technical name for the Group object is CollaborationGroup. |