My Oracle Support Banner

OIG Setting IncrementalField Of Extract Not Working Error: java.lang.RuntimeException: lastUpdatedDate, is not a (dynamic) field for class com.oracle.healthinsurance.activityprocessing.domain.internal.entities.ActivityMessageDomain (Doc ID 2656371.1)

Last updated on MAY 29, 2020

Applies to:

Oracle Health Insurance Enterprise Policy Administration - Version 3.20.1.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 3.20.1.0.0 version, Processing

When premium billing process is orchestrated by OIG and an invoked activity fails, OIG currently does not auto-retrieve the activity messages. Hence these activities need to be fetched with configuration.
Since the number of messages could exceed 200, the extract data collection step is used.

When creating an integration step of type 'Extract',the system adds a selection criteria lastUpdatedDate by default.
This leads to a technical error (see below). It is possible to override his behavior and define an incrementalField in the type config of the step. In this case, the activity.lastUpdatedDate is configured. But this incrementalField is not applied to the extract request. Therefore this step keeps running into the technical error.


ERROR
-----------------------
java.lang.RuntimeException: lastUpdatedDate, is not a (dynamic) field for class com.oracle.healthinsurance.activityprocessing.domain.internal.entities.ActivityMessageDomain


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1)  Create an extract integration step.
2)  Configure the incrementalField.
3)  Trigger the extract.
4)  Check extract metadata in OHI Policies.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.