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

count() fails with no field argument given (e.g. count(Id)) #1320

Closed
jungar opened this issue Dec 10, 2021 · 2 comments
Closed

count() fails with no field argument given (e.g. count(Id)) #1320

jungar opened this issue Dec 10, 2021 · 2 comments
Labels
bug Issue or pull request that identifies or fixes a bug investigating We're actively investigating this issue

Comments

@jungar
Copy link

jungar commented Dec 10, 2021

Summary

When using the builtin count() function in a SOQL query via sfdx, an error message similar to the below will be thrown unless a specific field is used as an argument to the function, e.g. count(Id) (see Steps To Reproduce for a complete, specific example)

(node:33946) Warning: The query result is missing 25300 records due to a 999999 record limit. Increase the number of records returned by setting the config value "maxQueryLimit" or the environment variable "SFDX_MAX_QUERY_LIMIT" to 25300 or greater than 999999.
(Use `node --trace-warnings ...` to show where the warning was created)

Steps To Reproduce:

Repository to reproduce: dreamhouse-lwc

NOTE: If your issue is not reproducable by dreamhouse-lwc, i.e. requires specific metadata or files, we require a link to a simple Salesforce project repository with a script to setup a scratch org that reproduces your problem.

  1. Log in to any SFDC Org from sfdx: sfdx force:auth:web:login
  2. sfdx force:config:set defaultusername (if necessary)
  3. Run a SOQL query on any object and use the count() function with no field argument, e.g.: sfdx force:data:soql:query -q "SELECT count() FROM PermissionSetAssignment WHERE PermissionSetId='0PS6T0000024uYe'"

Expected result

A count of all records should be returned, as per other tools which make similar SOQL API calls, and not an error.

Additonally, the error messaging "The query result is missing n records due to a y record limit" and "... n or greater than y" is pretty silly for values of y>=n ...

Actual result

Error message(s). See Summary, above.

System Information

  • If you are using sfdx

    • Run sfdx version --verbose --json

    jungar@jungar-ltm1 aloha_sfdx % sfdx version --verbose --json | jq { "cliVersion": "sfdx-cli/7.130.1", "architecture": "darwin-x64", "nodeVersion": "node-v16.13.1", "pluginVersions": [ "@oclif/plugin-autocomplete 0.3.0 (core)", "@oclif/plugin-commands 1.3.0 (core)", "@oclif/plugin-help 3.2.10 (core)", "@oclif/plugin-not-found 1.2.4 (core)", "@oclif/plugin-plugins 1.10.6 (core)", "@oclif/plugin-update 1.5.0 (core)", "@oclif/plugin-warn-if-update-available 1.7.3 (core)", "@oclif/plugin-which 1.0.3 (core)", "@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)", "alias 1.2.0 (core)", "apex 0.4.0 (core)", "auth 1.8.0 (core)", "config 1.3.0 (core)", "custom-metadata 1.0.12 (core)", "data 0.6.6 (core)", "generator 1.2.1 (core)", "info 1.1.2 (core)", "limits 1.3.0 (core)", "org 1.11.0 (core)", "salesforce-alm 53.6.0 (core)", "schema 1.1.0 (core)", "sfdx-cli 7.130.1 (core)", "source 1.6.2 (core)", "telemetry 1.4.0 (core)", "templates 52.6.0 (core)", "trust 1.1.0 (core)", "user 1.7.0 (core)" ], "osVersion": "Darwin 19.6.0" }

Additional information

@jungar jungar added the investigating We're actively investigating this issue label Dec 10, 2021
@github-actions
Copy link

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

@mshanemc mshanemc added the bug Issue or pull request that identifies or fixes a bug label Dec 10, 2021
@uip-robot-zz
Copy link

This issue has been linked to a new work item: W-10294697

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue or pull request that identifies or fixes a bug investigating We're actively investigating this issue
Projects
None yet
Development

No branches or pull requests

3 participants