Skip to main content

Hi everyone,
I'm working with the perform_hierarchy_select endpoint in the FSM OData API and trying to limit the number of records returned. 

This is the code I’m trying to use:
 


{
  "parameters": {
    "query": {
      "hierarchy_select": {
        "attrs": {
          "attr": r
            "task.task_id",
            "task.task_status"
          ]
        },
        "primary_table": "task",
        "from": {
          "table":  "task"]
        },
        "max_rows": 15
      }
    }
  }
}

 

Hi ​@jantonio,

Might be better to wait for one of the IFS Employees to comment, but I have been doing similar things in my role.

If using ODATA could you use a $top ‘x’ and $orderby ‘y’ to control that, and do the select through building the URL that gets posted.
I’m finding myself move towards that method instead of trying to do it in a hierarchy select perform.

An example of a post I have where I might have used the perform hierarchy select but now in using ODATA.

Hope that is a little helpful.


Ady

Reply


Terms & ConditionsCookie settings