Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
HDL - Element Entry Create record thinks it's updating an old one
Summary
even though I've supplied a unique SourceSystemId, HDL is trying to update an old, already end dated record insteadContent
Hello,
I'm a bit stuck at the moment. I have a .dat file whose intention is to create an Element Entry. I am using the SourceSystemOwner and SourceSystemId to generate the new user key for the record. My understanding is that I can use anything as my SourceSystemId, and then, under the covers, fusion updates all the necessary tables with what it needs in order to insert the record. To keep this SourceSystemId unique, I'm using a little formula : "ElementName_AssignmentNumber_EffectiveStartDate"
Tagged:
0