Learn how to use the Finder parameter in Oracle Fusion REST APIs instead of Q for better performance, cleaner OIC mappings, and optimized integrations.
While Finder works instantly in Postman, OIC requires it to be constructed as a single parameter using XPath expressions, that’s where most developers struggle
In OIC, integrating with Oracle Fusion Various REST APIs is a common requirement for extracting and processing business data. One of the key decisions developers face is how to filter data efficiently using query parameters.
Most developers are familiar with the q parameter, but Oracle also provides a powerful alternative the finder option.
What is finder in Oracle Fusion REST APIs?
The finder parameter is a predefined query mechanism provided by Oracle Fusion REST APIs to retrieve data using named queries and bind parameters
Eg:
...?finder=findPurchaseOrderSchedules;
bindPONumber=AE01-P001531;
bindPOItemNumber=664-8455
It behaves like parameterized SQL queries (bind variables), improving performance and readability.
What is q Parameter?
The q parameter is used to apply dynamic filters similar to a SQL WHERE clause
Eg:
...?q=PONumber='AE01-P001531' and POItemNumber='664-8455'
- Flexible but less structured
- Can lead to complex expressions
let's Walk into OIC......!
- Make sure you have required REST connections.
- Create Application based Integration with POST method.
Note:The below fields are we need to pass for another REST API.
- Call Get Method with finder using rest call.
Below reference, which we will call
Add Finder as review parameter for the endpoint
Now we will map to finder respectively as below.
End flow as below
TESTING
Top comments (0)