- UriNotMatchingException error for an Odata API call in SCPI/HCI
- org.apache.olingo.odata2.api.uri.UriNotMatchingException: Could not find an entity set or function import for 'Could be any Generic/MDF Object'
Reproducing the Issue
Run the SCPI/HCI artifact
Check the message processing log if it fails with 'UriNotMatchingException' error as shown below for your reference wrt. two MDF objects.
HCI tries to access the Object information from 'edmx' (local cache) for Odata entities and if it doesn't find corresponding field it fails out with 'UriNotMatchingException'.
Please follow below steps in order to resolve the issue-
1. Please check if the errored out MDF Object exist under 'Configure Object definition'.
a. If No, Customer has to configure the same first correctly. like in case of dataReplicationProxy, customer has to enable 'Payroll Integration (For On Prem Customers)' from provisioning, for position/employee time needs configuration under configure Object definition.
b. If yes, check if the API Visibility is set to true and has valid data available under manage data.
2. If Step b is also true, try the final step refreshing the Odata Metadata from admin center. You can refer the 'See also' part to know how metadata refresh happens.
UriNotMatchingException, Could not find an entity set or function import for, Odata metadata refresh , KBA , LOD-SF-INT-HCI , Standard SF to 3rd Party CPI (HCI) Content , LOD-SF-INT , Integrations , LOD-SF-INT-API , API & Adhoc API Framework , LOD-SF-INT-ODATA , OData API Framework , Problem