Multi-valued Distinguished Name (DN) attribute type transformation not working as expected.

DistinguishedNameConverted transformation is set as below for group

FOR IN [portalAccessMembers]
     DN:<span class="code-quote">"CN=[portalAccessMembers],DC=Parent"</span> -> [portalAccessMembersDN] 

PortalAccessMembers values are returned as multi-values. But PortalAccessMembersDN contains single value.

Edit (Adam): It appears that PortalAccessMembersDN contains many of the same value.

Adding a row manually to the schema requires you to browse to the connector options menu at the very top of the page and add from there. This is really annoying since the connector schema is at the bottom of the page

The Constant transformation has a feature to enter the type of value used for the constant. The default type is a Guid type field, and I am allowed to enter anything I want for its value. I am able to start an adapter with a constant value therefore populating a Guid field "newguid" with the string value "something". I was also able to do this with a date field. Depending on the type of field that gets mapped in FIM, I'm not entirely sure what would happen on an attempt to import this field - I imagine it would result in every entry failing with unexpected data, or possibly when committing the value to the adapter context.

Clicking the Load more connectors link expands the list of connectors until the page is refreshed by the ajax loader.

Creation of a new Connector:

Owner - Had to configure to 'dbo' for some reason, even though Owner was 'domainname\Administrator'

Edit (Adam): This is the owner of the table, in the format of a schema. A default install will have a value of dbo. The UI should be updated so that this is more obvious. Could dynamically get this from the connector as we have the details.

SELECT name, SCHEMA_NAME(schema_id) FROM sys.tables

I would like to get a better understanding/clarification of the sequence of events flow for Identity Broker as to when is the Adapter transformation being process. For example,

1. As part of Import in Unify Management Studio or per Connector's getEntity schedule (either a "Full Import" or "Synchronise Import"
   
   
2. During Adapter Entity Search in Unify Management Studio
   
   
3. During Import in FIM (either a "Full Import" or "Delta Import")

The Identity Broker's log file seems to indicate that the Adapter activities only take places during the last two events. Thus the reason for this question, as I would like to be able to answer a similar question when asked by customer.

When I create a Date-Relational Adapter the RangeEndColumn isn't being saved. It creates fine but when I click back into it the RangeEndKey value returns the default in the drop down list.

This seems to be caused by the configuration not being saved properly as uploaded. The RangeEndKey="00:00:00", it looks like it should equal the field name selected as with RangeStartKey="posstart".

Further, I edited the adapter config manually and restarted. It loaded in correctly so that the correct value was selected in the drop-down box but when I hit submit query then looked again it had changed back to the "00:00:00" value.

Currently unable to import Google Group settings (https://developers.google.com/admin-sdk/groups-settings/v1/reference/groups/get), not only in Identity Broker, but in the Google test explorer.

Have confirmed that the required scope has been applied to the account.

Group.PNG shows that the Groups are behaving fine.
GroupsSettings.PNG shows the error from Google.

In place text editors should be used where possible.

The following places are a minimum:

• Adapter general settings (name, comment, object class, base connector)
• Connector general settings (name, comment, queue when blocked)

Should probably be done using extension methods that are also available to connector developers so that they can have in place editors as part of the display template. May impact IDB-960. Think about user permissions also, but that may have to be extended when the "security enhancements" road map item is done.

This will also solve PRODUCT-261.

The following exception was being logged constantly in Matt's environment:

20121028,00:00:21,UNIFY Identity Broker,Void <.ctor>b__0(),Error,"An exception has occured whilst performing a job for partition 34b83581-377c-41b5-afb9-2a705076285f job ReflectAdapterOnChangeDueJob:
Unify.Framework.UnifyEngineException: The connector job ChangeDetectionSchedulerJobDecorator could not be run as the Chris21 Person Connector is currently disabled
   at Unify.Product.IdentityBroker.ChangeDetectionEnablementJobDecorator.<>c__DisplayClass2.<.ctor>b__0()
   at Unify.Framework.BeforeJobDecorator.Run()
   at Unify.Product.IdentityBroker.QueuedConnectorExecutionProcessorEndDecorator.Run()",Normal

Although it is describing the correct behaviour (an attempt to run a job was made, which required a disabled connector) the way in which it logged it was not useful, and would be worrying for implementers encountering this.

Firstly, this is not an Error, it is either a Warning or possibly information data. Secondly, considering it happens under the covers the logging level might need to be reassessed, as this will fill the logs quickly if the job is left unattended.