Yes, look for the `"@odata.nextLink"` in the JSON response when requesting an entity collection such as Assets. This is the URL you need to use to get the next page in the collection. See example at https://www.odata.org/getting-started/basic-tutorial/ for retrieving entity collections. Note that no cursors on expanded properties. I.e you should navigate to DataPoints and list the entity set, instead of expanding DataPoints within TimeSeries.
Hi, it’s correct that the OData service is specifically tailored as the backend for the Power BI connector. But it’s also a fully implemented OData API. However, the OData standard has many optional features, so two “compliant” OData client and servers may still not be able to talk with each other. The CDF OData service is self-describing so you (or an OData client) may inspect the service the following way:The service always returns the header: `odata-version: 4.0` as part of the HTTP response The service document lists the supported CDF resources (entity sets) relative to the service document: https://api.cognitedata.com/odata/v1/projects/publicdata/ The metadata document lists the schema in detail for each of the entity sets and specifies which queries are supported. https://api.cognitedata.com/odata/v1/projects/publicdata/$metadataNote that the two URLs above do not require authentication so you may click on them here with your web browser. But any query that returns data will requ
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.