Skip to Content
author's profile photo Former Member
Former Member

Query options $orderby, $inlinecount, $skip and $top cannot be applied to the requested resource

Hi Experts

I run the code I paste at the end of the Discussion with no problem, but if I want to display only one result

Instead of path: "/Orders",

I want to use path: "/Orders(10251)",

This error appears

Query options $orderby, $inlinecount, $skip and $top cannot be applied to the requested resource

If I run the call on the browser, and there is no problem.$expand=Customer

Is there any work around to display only one result also using the $expand





<meta http-equiv="X-UA-Compatible" content="IE=edge">

<meta http-equiv='Content-Type' content='text/html;charset=UTF-8'/>

<script src=""





<!-- only load the mobile lib "sap.m" and the "sap_bluecrystal" theme -->


var url = "proxy/http/";

var oModel = new sap.ui.model.odata.ODataModel(url, true);


var oTable = new sap.ui.table.Table("table", { // create Table UI

title: "Northwind - Orders",

columns : [

{label: "ID", template: "OrderID" },

{label: "Date", template: "OrderDate" },

{label: "Contact Name", template: "Customer/ContactName"}




path: "/Orders",

// path: "/Orders(10251)",

parameters: {



}); // bind the table rows

oTable.placeAt("content"); // place Table onto UI



<body class="sapUiBody" role="application">

<div id="content"></div>






Add comment
10|10000 characters needed characters exceeded

1 Answer

  • Best Answer
    Posted on Jan 13, 2015 at 07:07 AM

    Hello Henry,

    the binding path in that case must be a binding path to a list.

    You can restrict the binding by defining a filter:

    var aFilters = [];
    var oFilter = new sap.ui.model.Filter("OrderID", sap.ui.model.FilterOperator.EQ, "10251");

    The filter array (aFilter) then an be used in the binding (

    Best Regards,


    Add comment
    10|10000 characters needed characters exceeded

    • Hello Henry,

      it depends on your requirements 😉

      In your service just the read method (GET_ENTITY) was implemented, but not the query method (GET_ENTITYSET). If you have the requirement to display all "details" in e.g. a table than you could implement the method.

      Another point to consider is if the "details" entity is maybe related to a principal entity (e.g. SalesOrderItems are related to the principle entity SalesOrder). In such a case it would make sense to restrict the access to the depending entity via an association/navigation attribute between the principal entity and the depending entity (the restriction is done in the query method for the depending entity). This would result in following assuming we have a navigation attribute ToItems for the navigation from the principal entity to the depending entry (and the restrictions in the query method):

      - .../SalesOrderItems -> not allowed

      - .../SalesOrder('1000')/ToItems -> allowed

      But as written above, it depends on your requirements.

      Best Regards,