Release Notes > Summer 2016 - June > JD Edwards EnterpriseOne Connector
  

JD Edwards EnterpriseOne Connector

After You Upgrade

Copy the JD Edwards EnterpriseOne Third-Party Libraries to the Secure Agent Installation Directory

After you upgrade the Secure Agent, you must manually copy the JD Edwards EnterpriseOne third-party libraries from <JD Edwards EnterpriseOne 9.1 installation directory>\JDEdwards\E910\system\classes to two paths within the Secure Agent installation directory:

JD Edwards EnterpriseOne Connector Fixed Limitations

Review the Release Notes of previous releases for information about previous fixed limitations.
The following table describes fixed limitations:
CR
Description
CON-3851
When you use Secure Agent version 30.0 and later, and select a JD Edwards EnterpriseOne connection in a task to read from or write data to JD Edwards EnterpriseOne, the connection fails.

JD Edwards EnterpriseOne Connector Known Limitations

The following table describes known limitations:
CR
Description
CON-4189
Even though you have the option to configure a lookup for an LDAP object in the Cloud Mapping Designer while creating a mapping task, lookup is not supported for LDAP connector.
CON-4187
Even though you have the option to configure a lookup for an LDAP object in a Data Synchronization task, lookup is not supported for LDAP connector.
CON-3699
Even though the task is successful, the activity log displays a warning status.
Workaround: Ignore the warning.
CON-3192
When you configure a Join condition and include the Join operators other than equal for JD Edwards EnterpriseOne sources in tasks, an error appears stating that the expression string is invalid.
CON-2277
If you select JD Edwards EnterpriseOne views as the target object in a task, the Secure Agent fails to fetch the metadata and the task fails without displaying an appropriate error message.
CON-2176
You cannot edit the data types in a task.