Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pull more than 1000 results for box files:versions when using --json #220

Open
4 tasks done
Michael-B-23 opened this issue Nov 15, 2020 · 3 comments
Open
4 tasks done
Assignees
Labels
bug dontstale For stalebot to keep the issue open question

Comments

@Michael-B-23
Copy link

Michael-B-23 commented Nov 15, 2020

  • I have checked that the [SDK documentation][sdk-docs] doesn't solve my issue.
  • I have checked that the [API documentation][api-docs] doesn't solve my issue.
  • I have searched the [Box Developer Forums][dev-forums] and my issue isn't already reported (or if it has been reported, I have attached a link to it, for reference).
  • I have searched [Issues in this repo][github-repo] and my issue isn't already reported.

Description of the Issue

I'm trying to find out how to deal with a file that has more than 1000 versions when using --json. When running a box files:versions --json command, it only returns 1000 total, even if the file itself has more than that. We have some files with as many as 13000+ versions, and I'd like to figure out how to access them via powershell (mainly so I can delete them).

I don't know if there is a way to offset or paginate the returned array. If this is not possible, is there a way to access properties like foreach ($v in $version) {$v.created_at} without doing the --json | convertfrom-json thing?

image

Steps to Reproduce

$version = box files:versions FILEIDHEREWITHMORETHAN1KVERSIONS --json | ConvertFrom-Json
$version.count always equals 1000 (when --json is not used, it returns the correct amount)

Versions Used

Box CLI: 2.7.0
Operating System: Windows 10

@stale
Copy link

stale bot commented Aug 2, 2022

This issue has been automatically marked as stale because it has not been updated in the last 30 days. It will be closed if no further activity occurs within the next 7 days. Feel free to reach out or mention Box SDK team member for further help and resources if they are needed.

@stale
Copy link

stale bot commented Sep 8, 2022

This issue has been automatically marked as stale because it has not been updated in the last 30 days. It will be closed if no further activity occurs within the next 7 days. Feel free to reach out or mention Box SDK team member for further help and resources if they are needed.

@stale stale bot added the stale label Sep 8, 2022
@stale
Copy link

stale bot commented Sep 15, 2022

This issue has been automatically closed due to maximum period of being stale. Thank you for your contribution to Box CLI and feel free to open another PR/issue at any time.

@stale stale bot closed this as completed Sep 15, 2022
@mgrytsai mgrytsai added dontstale For stalebot to keep the issue open and removed stale labels Sep 15, 2022
@mgrytsai mgrytsai reopened this Sep 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug dontstale For stalebot to keep the issue open question
Projects
None yet
Development

No branches or pull requests

4 participants