Done
Details
Assignee
Azizbek KhushvakovAzizbek KhushvakovReporter
Brooks TravisBrooks TravisPriority
P2Story Points
1Sprint
NoneDevelopment Team
ThunderjetFix versions
Release
Ramsons (R2 2024)RCA Group
Implementation coding issueAffected releases
Quesnelia (R1 2024)Poppy (R2 2023)TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Azizbek Khushvakov
Azizbek KhushvakovReporter
Brooks Travis
Brooks TravisPriority
Story Points
1
Sprint
None
Development Team
Thunderjet
Fix versions
Release
Ramsons (R2 2024)
RCA Group
Implementation coding issue
Affected releases
Quesnelia (R1 2024)
Poppy (R2 2023)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created April 1, 2024 at 4:30 PM
Updated May 13, 2024 at 5:51 PM
Resolved April 9, 2024 at 5:04 AM
When calling
/consortia/<consortiaId>/tenants
, the “offset” query parameter behaves like apage
oflimit
rather than an actual offset. In addition, notenants
array is included in the response if offset pages pasttotalRecords
.Steps to reproduce:
On a folio tenant configured as the central tenant in an ECS deployment
Using a tool like Postman or cURL, make a call to
/consortia/<consortiaId>/tenants
without an offset and a limit of however many total tenants there areMake another call with limit=2 and offset=2
Expected results:
{"tenants": [{<tenant2>}, {<tenant3>}], "totalRecords": <totalRecords>}
Actual results:
{"tenants": [{<tenant4>}, {<tenant5>}], "totalRecords": <totalRecords>}
Additional Information:
This API is behaving very inconsistently to other offset/limit supporting APIs in FOLIO.