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.

Oracle HCM Cloud REST Endpoints best practice - PublicWorkers and Workers

Hi,

I am hoping to get advise on Oracle HCM Cloud REST Endpoints(GET) query best practice. I understand that one best practice is to query specific attribute (fields) instead of getting all the fields. I want to know if this may affect performance
→ if we are querying a lot of fields. Is there any limit on the number of fields to be queried that may affect performance.
→ If we use the fields attributes in combination with with multiple query(q) filters

Query example:
hcmRestApi/resources/11.13.18.05/workers?q=workRelationships.LegalEmployerName!='value' AND workRelationships.LegalEmployerName!='value' AND workRelationships.LegalEmployerName!='value' AND workRelationships.LegalEmployerName!='value' AND PersonNumber='value'

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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