I have a source date property for BirthDate which is appearing in the format CCYY-MM-DD, and when this is imported to FIM it is being treated as UTC time and is consequently shown with a local date/time offset value (i.e. + 10 hours in Sydney). I therefore need to find a way of subtracting the local time offset from the base value.

I have looked at the doco for this transformation https://unifysolutions.jira.com/wiki/display/IDB307/Time+offset+transformation and it appears to only cater for the reverse scenario - i.e. converting UTC to local. Is there a way to use this (or any other transformation) to subtract the local time from the base value?

Thanks.

Similar to https://unifysolutions.jira.com/browse/IDB-1132, it would be nice if the Timeoffset Flag transformation also had the ability to select days.

Currently the schema provider doesn't override fields with the same name. It would be useful following upgrades and whilst testing to have the schema provider override fields. Provide a boolean option that allows this to happen.

Look at IDB-935 at the same time.

Consider adding support for the database type of heirarchid.

Done:
When importing from the database connector where a type is not known, the following exception is generated:

System.Exception: A type converter is not available for type SqlHierarchyId.
at Unify.Framework.ObjectToValueAdapter.Transform(Object sourceValue)
at Unify.Product.IdentityBroker.ConnectorEntityFromDataRowConverter.Transform(DataRow sourceValue)
at Unify.Product.IdentityBroker.ConnectorEntitiesFromDataTableConverter.<Transform>b__0(DataRow dataRow)
...

The field name should be included in the exception details at the very minimum. Also consider adding support for new data types (including heirarchyid).

From the linked issue, in the entity viewer, some timestamps are displaying using a different date format to the others.
E.g. normal timestamps are formatted d/MMM/yyyy h:mm:ss, whereas the incorrect ones are using a default format - yyyy-MM-ddThh:mm:ssZ.

The timestamps that appear to be failing are DateTime.MaxValue.

Suspected error with the class EntitySerializer.

Only happen to the latest version

When viewing records in a connector, click on "Append Search Terms" above a column, the below error is displayed:

Error

System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: field
at Unify.Framework.Collections.GroupedNameValueCollectionKey.op_Implicit(String field) in c:\TeamCity\buildAgent\work\aad7920828b5b314\Source\Collections\Unify.Framework.Collections.Interfaces\GroupedNameValueCollection\GroupedNameValueCollectionKey.cs:line 197
at Unify.Connect.Web.IdentityBrokerEntitySearchController.AddEntityColumnSearch(Guid partitionId, String columnKey, String searchContext) in c:\TeamCity\buildAgent\work\77553fc70ab89549\Source\Studio\Unify.Connect.Web\Controllers\IdentityBrokerEntitySearchController.cs:line 543
at Unify.Connect.Web.Controllers.ConnectorController.AddEntityColumnSearch(Guid partitionId, String columnKey, String searchContext) in c:\TeamCity\buildAgent\work\77553fc70ab89549\Source\Studio\Unify.Connect.Web\Controllers\ConnectorController.cs:line 2534
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.<>cDisplayClass17.<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

The following is the exception message thrown when:

• An export is made to add an entity that exists in the connector context, but not in the adapter context
• The above, but also in the adapter context

Adapter request to add entity 1b0c3763-74f7-427f-a9d7-fa631b73f59f to adapter space 2d47c278-269c-4063-aff9-dad4548f8954 failed with reason Entity (DN: 'CN=6e5255c6-de86-632d-a6d2-c866f8f6027c') with key '6e5255c6-de86-632d-a6d2-c866f8f6027c' mismatch on Entity Id 1b0c3763-74f7-427f-a9d7-fa631b73f59f..

This message isn't descriptive of the problem, and more importantly covers up validation for breaking the key constraint on export; this doesn't break the validation as the export still fails, but it's not descriptive of the behaviour.

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.