data issue with OpenEdge native integration

Posted by Ollie on 08-Apr-2015 14:10

Hi,

Integrating Corticon with OpenEdge through the native connector is resulting in data corruptions. The cause of it has been traced to whether or not empty date fields are included in the call. When the OpenEdge program sends only the data elements that the decision service actually uses, the data is fine. If we add other data elements, but leave out all the unused date fields, the data still comes back fine. Adding all the unused date fields to the prodata set causes problems. After the call has been completed some of the data in the temp table will have changed to "?". This occurs not only in the date fields and it isn't limited to null values. The "?" occur in a variety of fields. Remarkably the county codes (string field containing number codes) will all have "?". transactionDate is only "?" on records where transactionEffectiveDate was originally "?", and transactionEffectiveDate came back unchanged.

I can't find any reason for this, nor is there any (obvious) regularity in the errors occuring.

All Replies

Posted by Peter Judge on 08-Apr-2015 14:20

It sounds like it might be a bug somewhere; please contact Tech Support.
 
If you run the OE client with –debugalert or session:debug-alert = true, you'll see a couple of files in the session's temp directory which contain dumps of the request and response to and from the Corticon server. Include those on the call if possible, as well as (at least) your temp-table/dataset definitions.
 
-- peter
 
[collapse]
From: Ollie [mailto:bounce-olafjanssensmhplancom@community.progress.com]
Sent: Wednesday, 08 April, 2015 15:11
To: TU.Corticon@community.progress.com
Subject: [Technical Users - Corticon] data issue with OpenEdge native integration
 
Thread created by Ollie

Hi,

Integrating Corticon with OpenEdge through the native connector is resulting in data corruptions. The cause of it has been traced to whether or not empty date fields are included in the call. When the OpenEdge program sends only the data elements that the decision service actually uses, the data is fine. If we add other data elements, but leave out all the unused date fields, the data still comes back fine. Adding all the unused date fields to the prodata set causes problems. After the call has been completed some of the data in the temp table will have changed to "?". This occurs not only in the date fields and it isn't limited to null values. The "?" occur in a variety of fields. Remarkably the county codes (string field containing number codes) will all have "?". transactionDate is only "?" on records where transactionEffectiveDate was originally "?", and transactionEffectiveDate came back unchanged.

I can't find any reason for this, nor is there any (obvious) regularity in the errors occuring.

Stop receiving emails on this subject.

Flag this post as spam/abuse.

[/collapse]

Posted by Ollie on 08-Apr-2015 14:30

Thank you. We're working on getting those file-dumps now.

This thread is closed