Hi All,
Is it possible to add the paging feature to a custom Rest API?
To give a bit more detail, when you click into the default CIMapping API via Swagger, you get a bunch of options. One of these options (the 3rd GET) allows you to specify a customer ID, page number, and page size filters to be applied to the results.
Is there a way to add these features to a custom API? Specifically the paging option.
Thanks,
Calvin
Solved! Go to Solution.
/rest/v1/cimapping is a different API than /rest/v1/data and so while cimapping allows different options, /data is based on PQL views created in the RestAPIDataset xml. It only allows you to specify url parameters that can be used in the PQL query. It may allow you to apply filters like 'TOP N' and where-clause and nodes etc, paging is not an option it currently supports.
/rest/v1/cimapping is a different API than /rest/v1/data and so while cimapping allows different options, /data is based on PQL views created in the RestAPIDataset xml. It only allows you to specify url parameters that can be used in the PQL query. It may allow you to apply filters like 'TOP N' and where-clause and nodes etc, paging is not an option it currently supports.
Thanks Shoaib, any idea if there are plans to add this feature in future releases?
Unified Communications has always been an important part of companies' digital transformation efforts due to its ability to enable rich virtual collaboration and communication. But with COVID-19, we've reached a break-through point.
Join Bill Haskins, Sr. Analyst & Partner, Unified Communications at Wainhouse Research, and John Ruthven, CEO at IR discuss UC challenges companies are experiencing due to the COVOID-19 crisis.
Join webinarMembers | Likes |
---|---|
23 | |
23 | |
14 | |
10 | |
8 |