We are experiencing an issue with the enrollments API pagination on DHIS 2.26 (it exists on the later versions of DHIS as well). When the enrollments API is paginated, it returns the enrollments for the given pageSize and the page number. But, it doesn’t return the pager params as a part of each page response, like it returns in other APIs. By pager params we mean, paging details like total, pageSize, page, pageCount.
Without the paging params it would be hard for us to figure out on how many pages should we download and also at which page we should stop downloading. Because of this issue, we are not able to paginate the enrollments API.
We are about to go live with programs with registration which would internally use the enrollments API. We are expecting a lot of data entry to be done in the near future. This means there will be a lot of enrollments in the system and downloading all of them in a single API call, would be problematic for our end users who are in remote locations with very slow internet connectivity.
Will you be able to fix the pagination of enrollments API to return the paging params, so that it is consistent with the other API’s paging response and we could also leverage it.
We are experiencing an issue with the enrollments API pagination on DHIS 2.26 (it exists on the later versions of DHIS as well). When the enrollments API is paginated, it returns the enrollments for the given pageSize and the page number. But, it doesn’t return the pager params as a part of each page response, like it returns in other APIs. By pager params we mean, paging details like total, pageSize, page, pageCount.
Without the paging params it would be hard for us to figure out on how many pages should we download and also at which page we should stop downloading. Because of this issue, we are not able to paginate the enrollments API.
We are about to go live with programs with registration which would internally use the enrollments API. We are expecting a lot of data entry to be done in the near future. This means there will be a lot of enrollments in the system and downloading all of them in a single API call, would be problematic for our end users who are in remote locations with very slow internet connectivity.
Will you be able to fix the pagination of enrollments API to return the paging params, so that it is consistent with the other API’s paging response and we could also leverage it.
We are experiencing an issue with the enrollments API pagination on DHIS 2.26 (it exists on the later versions of DHIS as well). When the enrollments API is paginated, it returns the enrollments for the given pageSize and the page number. But, it doesn’t return the pager params as a part of each page response, like it returns in other APIs. By pager params we mean, paging details like total, pageSize, page, pageCount.
Without the paging params it would be hard for us to figure out on how many pages should we download and also at which page we should stop downloading. Because of this issue, we are not able to paginate the enrollments API.
We are about to go live with programs with registration which would internally use the enrollments API. We are expecting a lot of data entry to be done in the near future. This means there will be a lot of enrollments in the system and downloading all of them in a single API call, would be problematic for our end users who are in remote locations with very slow internet connectivity.
Will you be able to fix the pagination of enrollments API to return the paging params, so that it is consistent with the other API’s paging response and we could also leverage it.
Yes @Morten, we tried paginating it by adding totalPages request param. But still, we don’t get the pager details (like total, pageSize, page, pageCount).
We are experiencing an issue with the enrollments API pagination on DHIS 2.26 (it exists on the later versions of DHIS as well). When the enrollments API is paginated, it returns the enrollments for the given pageSize and the page number. But, it doesn’t return the pager params as a part of each page response, like it returns in other APIs. By pager params we mean, paging details like total, pageSize, page, pageCount.
Without the paging params it would be hard for us to figure out on how many pages should we download and also at which page we should stop downloading. Because of this issue, we are not able to paginate the enrollments API.
We are about to go live with programs with registration which would internally use the enrollments API. We are expecting a lot of data entry to be done in the near future. This means there will be a lot of enrollments in the system and downloading all of them in a single API call, would be problematic for our end users who are in remote locations with very slow internet connectivity.
Will you be able to fix the pagination of enrollments API to return the paging params, so that it is consistent with the other API’s paging response and we could also leverage it.
Yes @Morten, we tried paginating it by adding totalPages request param. But still, we don’t get the pager details (like total, pageSize, page, pageCount).
We are experiencing an issue with the enrollments API pagination on DHIS 2.26 (it exists on the later versions of DHIS as well). When the enrollments API is paginated, it returns the enrollments for the given pageSize and the page number. But, it doesn’t return the pager params as a part of each page response, like it returns in other APIs. By pager params we mean, paging details like total, pageSize, page, pageCount.
Without the paging params it would be hard for us to figure out on how many pages should we download and also at which page we should stop downloading. Because of this issue, we are not able to paginate the enrollments API.
We are about to go live with programs with registration which would internally use the enrollments API. We are expecting a lot of data entry to be done in the near future. This means there will be a lot of enrollments in the system and downloading all of them in a single API call, would be problematic for our end users who are in remote locations with very slow internet connectivity.
Will you be able to fix the pagination of enrollments API to return the paging params, so that it is consistent with the other API’s paging response and we could also leverage it.