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.
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.
Flag this post as spam/abuse.
Thank you. We're working on getting those file-dumps now.