-
Notifications
You must be signed in to change notification settings - Fork 78
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
Add support for queryAll
#1959
Comments
Thank you for filing this feature request. We appreciate your feedback and will review the feature at our next grooming or sprint planning session. We prioritize feature requests with more upvotes and comments. |
This issue has been linked to a new work item: W-12590109 |
@surajp Thank you for filing this feature request. Seems like this would be a good addition to the query command! We will have to prioritize this work, so not sure when we would be able to get to it. We do accept contributions, so if you would like to do that please see CONTRIBUTING guide. |
This is now in the latest CLIs: sfdx 7.208.10 / sf 1.85.8 |
Is your feature request related to a problem? Please describe.
Currently, the CLI's
data:query
command does not seem to supportqueryAll
which is frustrating when trying to fetch deleted records, archived activities, etc.What are you trying to do
Fetch deleted records/archived activities.
Describe the solution you'd like
The
data:query
command should add support for anallRows
flag which would cause it to use thequeryAll
api instead of thequery
api.Describe alternatives you've considered
Currently, I resort to using Apex Dataloader or running an anonymous Apex script with
ALL ROWS
parameter. I've also built my own CLI plugin.Additional context
This should be trivial to implement, I think, since the version of
jsForce
the CLI is using seems to simply require ascanAll
flag to be set to true to usequeryAll
instead ofquery
. Additonally, settingautoFetch
to true seems to fetch all records as well by hitting thenextRecordsUrl
in a loop till all rows are returned.The text was updated successfully, but these errors were encountered: