Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Adding new attribute to existing changes only extract

Summary:


Adding new attribute to existing changes only extract leads to full volume run

Content (please ensure you mask any confidential information):

Hi Team,

Greetings!

We have an existing changes only extract which keeps extracting the daily data changes and writes them into the file, which is sent over the destination.

There is a need to add a new attribute (Seniority Date) to the existing extract.

What are the key steps to be handled when we move the change to Production?

We had observed in the past that addition of the new attribute ends up the first run in production to generate full file post deployment , even when the same set of input parameters used?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!