0
Answered

Import all entities from connector Chris21 Secondment Connector failed with reason Result record does not contain the required "status" attribute.

Jerry Natarajan 7 years ago in UNIFYBroker/Frontier ichris/chris21 updated by anonymous 5 years ago 8

Unify Identity Broker: 4.1.x

Unify Identity Broker Connector for chris21  :v4.1.x

Getting this error while importing all from Secondment Connector

Detailed error:
status="ok" expected. Line GTR,S60W71E1R U1903R54 3812 177M33II26S1 03:cbr="zsmlst",sendfields="D",showtranslation="s",filter01="zsmenddate:GE:2017-06-06:or",filter02="zsmenddate:EQ::",maxlines="1000",detnumber="10122",detnumber.trn="Dare H",zsmstartdt="2012-10-01",zsmenddate,zsmscdmthr="35.00",zsmcompany,zsmreptnam,zsmexplnth,zsmchgrate="
Chris21 GTR returned no additional error messages.. Duration: 00:00:02.4782478
Error details:
System.IO.InvalidDataException: Result record does not contain the required "status" attribute.
status="ok" expected. Line GTR,S60W71E1R U1903R54 3812 177M33II26S1 03:cbr="zsmlst",sendfields="D",showtranslation="s",filter01="zsmenddate:GE:2017-06-06:or",filter02="zsmenddate:EQ::",maxlines="1000",detnumber="10122",detnumber.trn="Dare H",zsmstartdt="2012-10-01",zsmenddate,zsmscdmthr="35.00",zsmcompany,zsmreptnam,zsmexplnth,zsmchgrate="
Chris21 GTR returned no additional error messages.
at Unify.Product.IdentityBroker.Chris21Agent.CheckStatusAttribute(IChris21CommandLine chris21GtrCommandLine)
at Unify.Product.IdentityBroker.Chris21Agent.ExtractListResult(ICollection`1 entities, IChris21Record record, IChris21ConnectorInformation connectorRequest)
at Unify.Product.IdentityBroker.Chris21Agent.<listwithchunking>d__4.MoveNext()
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at Unify.Framework.Collections.ActionOnExceptionEnumerator`1.MoveNext()
at Unify.Framework.Collections.EnumerableExtensions.<actiononlast>d__10`1.MoveNext()
at Unify.Framework.Collections.EnumerableExtensions.<produceautopages>d__7`1.MoveNext()
at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.Visit()
at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.PerformChangeDetection(IEnumerable`1 connectorEntities)
at Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.ImportAllChangeProcess()
at Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.RunBase()
at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run()
at Unify.Product.IdentityBroker.ConnectorJobExecutor.<>c__DisplayClass27_0.<run>b__0()
at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)</run></produceautopages></actiononlast></listwithchunking>


The emp id of 10122 terminated 30/6/2015. Not sure if this helps?

Also this particular secondment record has no end date

Answer

Answer

The connector checks that there is a status="ok" in each entry. I can't see how end date could have any impact on this. Try running the query in the GTR form for a couple of different forms and compare the output.

Under review
  • Is this a new connector or an existing one that has been in place for some time?
  • Has this full import operation worked before?
    • If yes, when did it stop working and what changed at this time?

This is an existing one that has been in place for sometime. Yes it was working before.

The only change that they saw was with The emp id of 10122 terminated 30/6/2015, whose secondment dont have any end date set.

i have also asked them to add end date and test.

Answer

The connector checks that there is a status="ok" in each entry. I can't see how end date could have any impact on this. Try running the query in the GTR form for a couple of different forms and compare the output.

Under review

You should be able to test using the command:

cbr="zsmlst",sendfields="D",showtranslation="s",filter01="zsmenddate:GE:2017-06-06:or",filter02="zsmenddate:EQ::",maxlines="1000"

Same issue is occurring for me - and quite possibly the same customer (just upgraded them to UNIFYBroker and the latest versions of everything).

Any chance we could put in a workaround flag, to tell the system to assume OK when the status="OK" is missing?  This is in their TEST environment, also only happening on the Secondment connector.

Even though there may only be one record that's missing the status field, all data from the import is ignored, so I can't run an Import All for them until something is sorted out.