Table of Contents

Search

  1. Informatica Bug Tracking System Change
  2. PowerExchange for Amazon Redshift
  3. PowerExchange for Amazon S3
  4. PowerExchange for Cassandra
  5. PowerExchange for DataSift
  6. PowerExchange for Facebook
  7. PowerExchange for Greenplum
  8. PowerExchange for HBase
  9. PowerExchange for HDFS
  10. PowerExchange for Hive
  11. PowerExchange for JD Edwards EnterpriseOne
  12. PowerExchange for LDAP
  13. PowerExchange for LinkedIn
  14. PowerExchange for MapR-DB
  15. PowerExchange for Microsoft Azure Blob Storage
  16. PowerExchange for Microsoft Azure SQL Data Warehouse
  17. PowerExchange for Microsoft Dynamics CRM
  18. PowerExchange for MongoDB
  19. PowerExchange for Netezza
  20. PowerExchange for OData
  21. PowerExchange for Salesforce
  22. PowerExchange for SAP NetWeaver
  23. PowerExchange for Tableau
  24. PowerExchange for Teradata Parallel Transporter API
  25. PowerExchange for Twitter
  26. PowerExchange for Web Content-Kapow katalyst
  27. Informatica Global Customer Support

PowerExchange Adapters for Informatica Release Notes

PowerExchange Adapters for Informatica Release Notes

PowerExchange for JD Edwards EnterpriseOne Known Limitations (10.1.1)

PowerExchange for JD Edwards EnterpriseOne Known Limitations (10.1.1)

The following table describes known limitations:
Bug
Description
PLAT-14745
If the Integration Service writes rejected rows followed by valid rows to an interface table, the row statistics generated for an InterfaceWrite operation is incorrect. (442266)
PLAT-14732
When you apply a native filter expression for data that contains the JDE date data type format that is not valid, the data preview and mapping does not fail. An appropriate error message does not appear when you use formats that are not valid.
Workaround: Do not use the yyyy-mm-dd hh:mm:ss and hh:mm:ss date formats. Instead, use the yyyy-mm-dd format. (439302)
PLAT-14730
When you import a table that contains the ID_LONG data type, the Integration Service fails to import some of the table columns. (439071)
PLAT-14724
Even when the error threshold is reached, the Integration Service continues to process the data and mapping does not fail. The issue occurs because the Stop On Errors run-time property does not work. (437824)