CR | Description |
---|---|
ICS-5165 (formerly INFA 392733) | Tasks that use a $LastRunDate to filter SQL Server 2012 source data fail. |
ICS-5167 (formerly INFA 366567) | Do not use data filters or perform lookups with Oracle or SQL Server connections that use the following code pages:
|
ICS-5168 (formerly INFA 366566) | Do not use the following code pages for any connection type except flat file, Oracle, and SQL Server. The following code pages display for other connection types, but are not valid code page options:
|
ICS-5184 (formerly INFA 376289) | The Mapping Configuration task rejects flat file rows that include newline characters within a field when all source fields are not included in the data flow. Workaround: Include all source fields in the data flow. Even if you do not need all fields written to the target, use a field rule to include all fields to the first transformation after the source. If necessary, you can add an Expression or Filter transformation to handle this issue. |
ICS-4536 | SQL transformations cannot accept incoming fields from more than one transformation at a time. Workaround: Add an Expression transformation as an upstream transformation to the SQL transformation to take the input links from the multiple transformations. |
ICS-2869 | You can use PowerCenter workflows with flat file, database, web service, NetSuite, Salesforce, Oracle On Demand, and Microsoft Dynamics connections in PowerCenter tasks. All other connection types are not supported. |
CR | Description |
---|---|
INFA326881 | Due to a JDBC driver limitation, the driver returns the Microsoft SQL Server 2008 Nvarchar(Max) field as Ntext and returns Varchar(Max) field as Text. As a result, Nvarchar(Max) or Varchar(Max) fields do not display in data filters. Workaround: Enter the fields manually in an advanced data filter. Or, on the Field Mappings page, use the Edit Types option to edit the data types. Update incorrect Ntext fields to Nvarchar and incorrect Text fields to Varchar. |
CON-3239 (formerly INFA INFA327711) | Due to an Oracle CRM On Demand limitation, you cannot use custom objects 4-15 with Data Synchronization tasks. |