Feature Request Summary:
When downloading from the Users API, the number and order of columns should remain the same on each page of results.
Description/Use Cases:
When you are trying to do a GET of something like users or agents, there is a limit of 100 per page. This is cumbersome, but made even worse by the fact that every page has a different order for the columns of data, and some pages have less columns than others. This makes compiling the pages into a single spreadsheet a messy nightmare. For instance, I downloaded and checked on agents “last login date”. The last login date “column” when converted from JSON, was this:
Sheet 4: Column W
Sheet 3: Column AD
Sheet 2: Column AQ
Sheet 1: Column AY
This is madness and a huge waste of time, and robs me of an easy way to append these back together into a single document. I waste so much time trying to deal with keeping each “page” of results separate and doing the task I need to do per page, rather than try to do deal with getting the columns correctly aligned and appended into a single sheet. It also makes it quite more complex to try and code an automatic solution for the “100 results for page” problem. There's a lot of clever things I could do with parsing the details in the many, many columns provided, but it's not worth my time to write a script to do it for me, or alternatively sort over 100 columns, per 100 results, every time I want to look at or manipulate the data.
Business impact of limitation or missing feature:
This would help save a lot of time and make the API a lot less infuriating to work with.