Hi,
my aim is to find all documents in a specific folder and do this paginated.
Therefor I want to use the SDK method "findPaginated". This method gets a parameter QueryParams. I used setPath on the QueryParams to set the path.
The result is null everytime. So I started to investigate the REST endpoint which is called by the SDK. It looks like this (without annotations).
My question is, why? Why can I specify a path in QueryParams that is never used for a query. And how may I get all documents of a specific folder with pagination?
And yes, we need pagination, because a folder can contain thousands of documents.
Thank you!
my aim is to find all documents in a specific folder and do this paginated.
Therefor I want to use the SDK method "findPaginated". This method gets a parameter QueryParams. I used setPath on the QueryParams to set the path.
The result is null everytime. So I started to investigate the REST endpoint which is called by the SDK. It looks like this (without annotations).
Code: Select all
So you can see, there is no path left. The path in QueryParams is set to null in the REST endpoint.public ResultSet findPaginated(int offset, int limit, String content, String name, int domain, List<String> keywords, List<String> categories, List<String> properties, String author, String mimeType, String lastModifiedFrom, String lastModifiedTo, String mailSubject, String mailFrom, String mailTo)
My question is, why? Why can I specify a path in QueryParams that is never used for a query. And how may I get all documents of a specific folder with pagination?
And yes, we need pagination, because a folder can contain thousands of documents.
Thank you!
