-
Notifications
You must be signed in to change notification settings - Fork 1
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
Paging - Get-IBResourceRecord #2
Comments
Hi, I finally received something that looked like proper documentation of the API the other day, so I will try to start working on this project again soon, sadly, time has not been on my side lately. I would really love some help with this project, so if you create new cmdlets/fixes and want to contribute, you are more than welcome :-) Take care! |
Hi! I finally had time to sanitize and clean up some of the code for this. My code is a bit crude, and there's a good bit of it, ended up creating a separate repository. If you're still working on it and it would help, feel free borrow from it. Thanks for the ideas and examples in your code, it was quite helpful! |
Hi again :) My code also needs a bit (a lot) of cleaning up, I created it mostly to try to find other people interested in helping out :-) I've had quite a lot of interest in using the module, but not so much in developing it... So if you are going to keep working on it, we could try to share the burden... :-) But it seems you, just like me, have other priorities right now. So we'll see I guess :-) |
First, thanks for posting this code, very helpful and practical for getting started!
Just a heads up, it looks like if more than 1000 results are returned from Get-IBResourceRecord, we get an error 400.
An example solution:
First request: use _paging=1, _max_results=, _return_as_object=1 for the first request
All other requests: _page_id=<next_page_id from previous page of results>
I ended up using the pseudologic above and always force paging with a default of 1000 max results.
Cheers!
The text was updated successfully, but these errors were encountered: