Chris21 Connector Failing - no status attribute

Daniel Walters 1 year ago in UNIFYBroker/Frontier ichris/chris21 updated by Matthew Davis (Engineering Manager) 1 year ago 7
I'm getting the exact same error as in this ticket https://voice.unifysolutions.net/communities/6/topics/3223-import-all-entities-from-connector-chris21-secondment-connector-failed-with-reason-result-record

From the looks of things it's the exact same issue at the same customer. I don't know if Jerry ever resolved it. I've attached the log entry that's showing the error. It's using Idb and Chris 21 versions 4.1.x. Their Chris21 instance is version 8.16.17.

Adam suggested running some Chris 21 query as a resolution but I'm not sure where that query should be run. Is this likely to be a misconfiguration of Chris21 or something with IdB? This is in a test environment.

Please let me know if you need any more information.

Affected Versions:
Fixed by Version:

Thanks. So it's an issue with what Chris21 is returning.

It appears that way. I've emailed my contact, hopefully I hear back soon. The client could also raise a support call if they need to expedite it, or they could re-save the failing items as that appeared to correct the issue when Jerry was looking at it.

Under review

As per the screenshot (private comment), the client had found an issue with some items that were not returning the ok status. They could rectify it by re-saving the items, but obviously not ideal to have to keep doing this. I'll check in with our Frontier contact to see if they know anything about this.

I have heard back:

I am not aware of any such problem.
All GTRs should return either status=ok or status=fail.
try going into the ZSM form in the chris21/ichris interface and see if they can recreate the problem.
Depending on how the form/file is created the user might need to select "Merge Lists" and choose "Sort by" to get the correct key of access for the list.
Or the GTR that is causing problems can be entered into the chris21 GTR form.
The customer can then refer the errors to the helpdesk.

If there aren't errors, but instead just missing the status flag, that should be forwarded to helpdesk as well.

Hi Daniel,

Have you had a chance to resolve this one?

The ticket can be closed. I notified the customer of the workaround and also passed the note from Frontier onto their Chris21 people so they can raise it with the Frontier helpdesk.