Multivalue DN generator transformation contribution breaks

Matthew Clark 12 years ago updated by anonymous 9 years ago 10

When the relational connector is updated for the multivalue DN generator transformation, the changes register errors with the following:

Changes register item processing on failed.
Changes register item processing on connector CSV Test failed with reason The column GroupMulti cannot be used to form a chained transformation.. Duration: 00:00:00.0322266
Error details:
Unify.Product.IdentityBroker.ColumnBlacklistedException: The column GroupMulti cannot be used to form a chained transformation.
at Unify.Product.IdentityBroker.MultiValueSourceEntityDistinguishedNameGeneratorTransformationFactory.ApplyChangeDetectionColumnInformation(IAdapterColumnSources columnInformation)
at Unify.Framework.Visitor.VisitT(IEnumerable`1 visitCollection, Action`2 visitor)
at Unify.Product.IdentityBroker.AdapterEngine.CreateColumnSources(IAdapterEntityTransformationFactory factory, IEntitySchema baseSchema, Guid baseConnectorId, String adapterName, Guid adapterId)
at Unify.Product.IdentityBroker.AdapterEngine.<>c_DisplayClass27.<GenerateAdapter>b_23()
at Unify.Product.IdentityBroker.ChainedTransformationChangeProcessor.PublishChange(IEnumerable`1 changedEntities, DateTime changeProcessTime, ICollection`1 changeRecords)
at Unify.Product.IdentityBroker.ChainedTransformationChangeProcessor.ProcessChangeReport(IDictionaryTwoPassDifferenceReport`4 changesReport, DateTime changeProcessTime)
at Unify.Framework.Visitor.VisitT(IEnumerable`1 visitCollection, Action`2 visitor)
at Unify.Product.IdentityBroker.ChangeReportProcessor.CreateAndProcessReportT(IEnumerable`1 adapterTransformationProcessors, IEnumerable`1 sourceEnumerable, DateTime changeTime, Action`2 addAction)
at Unify.Product.IdentityBroker.ChangeReportProcessor.ProcessReport(IChangeReportProcessingRequest request)

Matthew, where does this GroupMulti field come from? ie what transformation has created it?


Assigned to Tony.

By "updated" above, I mean a connector import pulls in new data, not that the configuration has changed.

Schema validation will need to be updated to check whether blacklisted values will be used.

As mentioned, this is a minor schema validation issue and can be pushed up to beta as such.

AvV: Once you have looked at the UI side of this issue, please assign back to me to look at the blacklisting.

It seems as though blacklisting would have been used to protect left side keys from being updated/removed, as the eventual generated contribution collection is a flat dictionary (and not calculated at each step). However the Remove method on the Column Sources isn't being used anymore, and no Column Sources are updated; as such the blacklist requirements have been removed.

This has been confirmed locally - reassigned for confirmation of completion.

Confirmed and tested change detection for this transformation in the latest build of the service. Closed.