Filtering by status works in /activities API but not in resource route — is this expected? — Cloud Customer Connect
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

Filtering by status works in /activities API but not in resource route — is this expected?

in Field Service 2 comments

Summary:

Hi Community,

I’m currently working with Oracle Field Service REST APIs using Postman to test endpoints.

I noticed a difference in how filtering behaves between these two APIs:

✅ GET /rest/ofscCore/v1/activities

This endpoint supports filtering via the q parameter. For example, the following works perfectly in Postman:

q=status == 'completed'

It correctly returns only completed activities.

❌ GET /rest/ofscCore/v1/resources/{resourceId}/routes/{date}

When I try the same filter here:

q=status == 'pending'

The response still includes all activities for the resource on that date, regardless of their status. It seems the q parameter is ignored.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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