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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Time Record Event Requests - HCM Api - timeRecordId required for UPDATE call
Summary:
For HCM Rest Api - Time & Labor:
On Create Timecard, using Time Record Event Requests REST Endpoints, POST api, the result consists of-
timeRecordEventRequestId & timeRecordEventId
To Delete or to Update, timeRecordId is required which is obtained via
GET call /hcmRestApi/resources/11.13.18.05/timeRecords?
providing week start date, end date & person_id.
Response consists of unique timeRecordId for each day.
For ex: in below timeRecordEvent for each 4hr will get its unique timeRecordId on Get call for this week.
02/28 03/01 03/02 03/03 03/04
Project1 4hrs 4hrs 4hrs 4hrs 4hrs
Project2 4hrs 4hrs 4hrs 4hrs 4hrs
For a time card Event with multiple projects & dates, how is timeRecordId correctly identified?
0