Symptom
Query string filters and customized operations are not available as a selection in the ‘Model operation’ step of the SF Odata V2 Adapter.
Sample use case : The user wants to use string function 'does not start with' as filter in the Odata API request.
Environment
- SAP Susccessfactors HXM Core
- SuccessFactors OData V2 Receiver Adapter
Cause
Product Feature Limitation
Resolution
These filters can be directly defined into the ‘Processing’ tab > ‘Query Options’ when you configure your SF CPI ODATA adapter in the artifact.
In this example, string function ‘does not start with’ can be written as, ?$filter=not startswith(username,'j'). ‘j’ in this filter is just an example.
See Also
1. Other Odata API Supported filters syntax samples.
starts with > $filter=startswith(username,'<filter_value> ')
ends with > $filter=endswith(username,'<filter_value> ')
does not end with > $filter=not endswith(username,'<filter_value> ')
trim is equal to > $filter = trim(username) eq '<filter_value> '
to upper case is equal to > $filter=toupper(username) eq '<filter_value>'
to lower case is equal to > $tolower(username) eq '<filter_value>'
See all syntax in SAP SuccessFactors HXM Suite OData API: Developer Guide (V2) > under $filter section
2. See guide for How to 'Configure the SuccessFactors OData V2 Receiver Adapter'
Keywords
Susccessfactors Odata API $filter string function, customized operation, CPI Adapter, SuccessFactors OData V2 Receiver Adapter , KBA , LOD-SF-INT-CPI , Standard SF to 3rd Party CPI (HCI) Content , LOD-SF-INT , Integrations , LOD-SF-INT-ODATA , OData API Framework , How To