When all DN components are deleted, the DN generator defaults to either the Schema Key or the Entity Id generator (depending on the schema key). When you attempt to delete this one in a transformation, you receive a "Sequence contains no elements" message in the temp data message. This has no operational impact other than this message appearing in this case.

However, this also occurs when attempting to delete a component from a multipart component results in the same error, and this does affect configuration. You can work around this currently by deleting the multipart completely and recreating it.

Functions menu for the MultiValue Union transformation errors with:

System.NullReferenceException: Object reference not set to an instance of an object.
at Unify.Connect.Web.AdapterController.EditTransformationOnStep(Guid id, Guid transformationId) in c:\workspaces\IdentityBroker\Source\Studio\Unify.Connect.Web\Controllers\AdapterController.cs:line 1294
at lambda_method(Closure , ControllerBase , Object[] )
at System.Web.Mvc.ActionMethodDispatcher.Execute(ControllerBase controller, Object[] parameters)
at System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters)
at System.Web.Mvc.ControllerActionInvoker.<>c__DisplayClass15.<InvokeActionMethodWithFilters>b__12()
at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation)
at System.Web.Mvc.ControllerActionInvoker.<>c__DisplayClass15.<>c__DisplayClass17.<InvokeActionMethodWithFilters>b__14()
at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodWithFilters(ControllerContext controllerContext, IList`1 filters, ActionDescriptor actionDescriptor, IDictionary`2 parameters)
at System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName)

In a similar vein to issues with MOSS 2007, SharePoint 2010 does not appear to handle symbols correctly. In the latest chris21 demo environment, regular ampersands were being correctly sent to SharePoint as the correct symbol '&'

&

but coming back as the wide Unicode symbol '＆'

＆

causing cycling exported-change-not-reimported errors

When installing a new version of IdB - if it finds config files in the Extensibility folder could it not overwrite them please? I thought this is how it worked before, but have just lost my config installing 3.0.8.

As is possible for Event Broker, it would be a significant improvement for an IdB operator to be able to set the logging level - in Windows Event Log terms this would equate to the following (from none to full logging):

None - Information - Warning - Error - Critical - Verbose

While there is no capability to wind the IdB logging level up and down, it would be expected that 1000s of events will be generated daily, even when no exceptions are being thrown. Regardless of the method chosen for logging, this is a deployment issue because it uses up resources unnecessarily and makes speedy identification of non-informational logs more difficult. This is especially true when logging to the Windows Event logs.

If a connector has been configured with a schedule that would never run, it would be good to have some additional feedback on this on the connector page. The only way you can see if this is the case is if you mouseover the little clock on the home page. It would be good if some additional UI feedback is given, either in the form of:

• Information on the schedule display stating that a particular schedule would never run
• An alert to the home page that such a configuration exists
• A header on the connector page stating the connector won't run
• A combination of these

In testing for IDBCHRS-34, it has been found that some instances of the Chris21 connectors were correctly committing entities to the database, while some are not. Debugging shows that the connector is correctly pulling entities from the target system, meaning these are being lost before committing to the database.

UPDATE: This was found to be an issue with schema validation causing the commit to fail on the "IncludeItem" step. However, the feedback to the user at the moment is insufficient, and you can only find this by viewing the Identity Broker logs. The following should be added:

• A warning message should be raised and displayed on the statistics page - for v4.0, this should point the user to the logs. A larger set of work would be to collect all the entities that failed validation and display this following an import.
• Raise an alert with the alert engine
• The following error message should be updated to include the schema key for readability and ease of use, rather than the Entity Id:

The entity 55d751c6-0409-4bc0-9e09-1302e715feef on the f3df77ea-0084-4480-84a7-02125264899d connector Chris21 DET failed validation 3 times for the following reasons: detbirdate is a required field and is not present.; detsex is a required field and is not present.; detterdate is a required field and is not present.

When attemping to delete join mappings on idb4.1 I receive "The resource cannot be found"

Currently unable to configure joins without this ability

Screenshots provided:

A connector full import/sync that results in a large number of deletions (> 500,000) will abort its respective encompassing TransactionScope.

The following was additionally observed when the TransactionScope was observed to abort:

• When debugging, the TransactionScope itself is registered as complete. (TransactionScope::complete = true)
  • From this, it can be potentially inferred that the problem itself happens either on the MSDTC or SQL Server end - as far as the IdB application is concerned, the TransactionScope completed.
• The exception was thrown during IDB ChangeDetection.
• If debugging, ensure that break on all exceptions is enabled.
• During the import, in the respective SQL traces, a substantial number of entries were logged with the following EventClass and ApplicationName.

  EventClass: Lock:Timeout
  ApplicationName: .Net SqlClient Data Provider
  

With the latest build of Framework, the following error appears when trying to run an adapter full import using ECMA 1:

This is appearing in the serialization/ECMA 2 branch, but may also be occurring in default.