Table of Contents


  1. Abstract
  2. Installation and Upgrade
  3. 10.1.1 Fixed Limitations and Closed Enhancements
  4. 10.1.1 Known Limitations
  5. Informatica Global Customer Support

Informatica Connector Toolkit Known Limitations

The following table describes known limitations:
When you use
data type in a filter operation, you cannot test the read capability of the adapter.
Workaround: Use the Developer tool to test the
data type. (438209)
When you create native metadata objects with the same name but different letter case, the code generation fails.
Workaround: Use different names for different native metadata objects. (438203)
When you edit a connection attribute that has dependent fields, the test connection wizard does not display the changes made to the connection attribute. (435998)
When you add record extension attributes to the
method, the adapter does not get values for the record extension attributes at run time.
When you create an attribute for a native metadata object of type String with
Max Length
set to 255, the
Max Length
of the attribute is set incorrectly to 4000 after code generation.
If you specified
Enable Upsert Support
and implemented upsert operation for the adapter, at run time there is no tool tip to suggest the value that you need to specify for the
Workaround: You can specify one of the following values for the
attribute at run time:
  • Update As Update
    . If you specify the Update As Update value, you must implement the upsert logic so that the adapter updates an existing row while writing to the target.
  • Update Else Insert
    . If you specify the Update Else Insert value, you must implement the upsert logic so that the adapter updates an existing row if the row exists in the target, else inserts a row while writing to the target.