The newly created API for basic employee details, returns an error when filtering by emailAddress. If i however change the filter property to just “email” it works, but this is misleading considering the property is not mentioned in the EmployeeDetailsModel resource.
Can someone look into this please.
thanks
Great that you have a workaround Jon. As you are no doubt aware OData uses the underlying domain model to query against which in this instance does not match our View Models. We will add an item to our backlog to map an alias for emailAddress to email. Thanks for raising it!
Hi Ash,
The same happened recently with ExternalId vs ExternalReferenceId. Might i suggest that instead of just looking at the immediate emailAddress, that the backlog item review the OData policy and make sure ALL Api’s are correct.
thx