It's pretty easy to miss the fact that you have to update the connector after the schema is updated, a yellow bar similar to that used in the standard warnings above the schema mappings would help this.

The error from Chris21 is passed straight through to the IdB UI and displays the password.
I don't think this is desirable.

Enable the connector to fetch the names of available Chris21 forms on configuration. We could use the scripted dropdown control so that it does not become cumbersome to navigate the hundreds of forms available by default.

Estimate includes restructuring the UI for the required multi-step approach, and research into how to retrieve form details via GTR.

The Service Account user is not created in the Database and therefore the service cannot start. I would expect that the user would be created if the database is being created.

Because of the use of the GetObjectClass method which uses an object's DN to work out which schema it should use, new objects are not found for added entities exported to the adapter. The following error is thrown:

For adds, the adapter should be checking for the presence of the objectClass attribute exclusively (which is present in the LDIF).

After adding a schema field with the same name as an existing field using a relational and date relational transformation, I was unable to modify any transformations, with the reason being "An item with the same key has already been added". Manually removing the transformation from the config and restarting the service resolved the issue.

If you add a "Length" search term using the UI in the Entity Search, it clears the other search terms and does not search.

An import against a connector with entities that fail validation will generate changes even for those failing entities.

My setup currently has two connectors:

• e5d00f42-3725-4897-b909-73149f22c8cd (tony)
• 69e858d9-ef5e-488b-88cb-a75f3a8a1ed5 (AR)

One adapter:

• b78abc46-dc95-40d8-a2ef-37fcf2986e82 (AR Adapter)

An import against AR generates 20 changes for the 20 entities that are failing validation.

Each time, 20 entries appear in the changes table, with entity id's that cannot be found elsewhere in the database.

I had an error on my CSV connector - incorrect number of columns. Its put the next to it to denote the error. The error is resolved and several successful imports have occured but the icon is still there.

How long until it disappears automatically?

This appears on the home page. Its not on the Connectors page at all.

After updating the name of an adapter that had been added to an adapter group, the adapter disappeared from the group membership. Attempting to update the group details or memberships following this resulted in the following error: