OData property
Property not found in OData request
Gateway rejects a request because a property used in $select, $filter, payload or path is not defined for the addressed entity type.
Quick answer
- Most likely cause
- Client uses a field name that differs from the metadata property.
- Check first
- $metadata property names for the entity.
- First resolution step
- Use the property name exactly as exposed in metadata.
Likely root causes
- Client uses a field name that differs from the metadata property.
- Service model changed but client code still references an old property.
- Request addresses the wrong entity type.
What to inspect
- $metadata property names for the entity.
- Request URL/payload and exact casing.
- Recent service-model changes or regeneration.
Resolution path
- Use the property name exactly as exposed in metadata.
- Update the client after service contract changes.
- Expose a missing property only if it belongs in the API design.
- Retest filter/select/payload independently.
Share this diagnosis
Paste a credited summary into a ticket, chat or forum reply. Your pasted input is never included.
ERPClimb is an independent platform and is not affiliated with SAP SE.