10

There is --resultformat on query. sfdx force:data:soql:query -q "SELECT Id,Name,Status__c FROM Property__c" --resultformat csv` I got that from the command help. See below. -> sfdx force:data:soql:query --help Usage: sfdx force:data:soql:query -q <string> [-t] [-r <string>] [-- perfloglevel <string>] [-u <string>] [--json] [--...


8

Yes, the DX CLI can run on Heroku. Wade Wegner contributed this buildpack here: https://github.com/heroku/salesforce-cli-buildpack EDITED: added some extra details on how to install it since the readme is minimalist and outdated: 1) create the Heroku app heroku create 2) Set the buildpack heroku buildpacks:set https://github.com/heroku/salesforce-cli-...


6

Looks like promote commands reports success status before the package gets actually promoted, so ISV should wait some time up to an hour to wait until the package gets actually promoted


5

You're right that you cannot output to to CSV, but every command on the Salesforce DX command line has a JSON output option by using the --json option or setting a parameter to make DX default to JSON output as can be seen in the docs. Once you've done this, you have a well structured predictable data structure to convert to CSV, and there are a lot of ...


5

The source code for the CLI tool is available on GitHub. You could use that to investigate why the popup isn't occurring. In particular, start from the ForceLogin method. You could also raise an issue there to get product specific support. Maybe try the following syntax to do a credential based login. It might be that you're having problems popping up the ...


4

This is a known issue as of now (acknowledged by Dave Carroll from Salesforce). I also see your comment on this thread. The workaround suggested to dump the output into CSV/ JSON and use external tool such as 'q' worked fine for me. So, you should do something like this force query select name,ID from account limit 3 > account.csv q -H -d, 'select name,...


3

Ok, looks like I have to create Developer Edition org and register a namespace there and then link it to my Dev Hub org due to documentation https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_reg_namespace.htm


3

Run the following command first export SFDX_AUDIENCE_URL=https://test.salesforce.com Then run sfdx force:auth:jwt:grant --clientid <myclientid> --jwtkeyfile server.key --instanceurl https://mysandbox.my.salesforce.com --username <myusername> --setalias PraveenDevJWT Running the above-mentioned commands, worked for me. Thanks.


3

I don't see it in the source in query.go in the runQuery method: func runQuery(cmd *Command, args []string) { force, _ := ActiveForce() if len(args) < 1 { ErrorAndExit("must specify a query") } var query = "" if args[len(args)-1] == "format:json" { query = strings.Join(args[:len(args)-1], " ") } else { ...


2

I find it helpful to have the SOQL in a text file, and then use ` and cat to inject it into the command: force query "`cat mysoql.txt`" --format:csv >myresults.csv


2

$ force query "SELECT Sales_Order__c, Name FROM Opportunity" --format:csv


2

It requires force-cli which leads me to believe you have to have the force-cli be executable in your environment's path variable. You can test if Sublime is able to reach the force-cli by opening a command window and testing the following command. force whoami If not, find the location of the installed force binary and add it to your Windows path. There ...


2

When running data loader from the command line you are running an app that is using the Salesforce API to write data to Salesforce. If you want email notification on failures, the way to do that would then be through the app, or by way of the process that invokes the app (the batch or shell script that invokes the cli). At a high level you would want ...


2

If in doubt, go to the source - import.go. As it stands now this command won't be smart enough to diff what you have locally with what is currently in Salesforce a perform the required destructive changes. It is going to do a standard Metadata API deploy call. I think the best it can do is the -autoupdatepackage, -u option to: Auto add files to the ...


2

There are three parts involved here: The AsyncApiJob Id - 750 keyprefix - The Job The AsyncApiBatch Id - 751 keyprefix - The Batch The AsyncApiQueryResult Id - 752 keyprefix - The Batch Result You appear to have the first two parts, but not the AsyncApiQueryResult Id that will be used to retrieve the actual CSV. In terms or raw bulk API calls you need to ...


2

This error means that either the mdapipackage folder you're referencing in your command does not exist or that it does exist and it does not include a package.xml file. From your command history it appears that you are running the command from inside of the mdapipackage folder. The command looks for the mdapipackage folder inside of your current working ...


2

The only way I can think of to do this is to build a package.xml using version 39.0 (?) or lower (so that you don't get all the profile metadata), and explicitly specify which object/fields you want to retrieve. This should provide you with usable profiles that you can use to deploy other places. Unfortunately, if you have a complicated setup, like we do, it ...


1

You've copied-pasted something incorrect or such. You are not allowed to have a variable shadow another variable this way. Here's a non-compiling script that demonstrates this: public class q246196 { public void test() { String s; if(s == null) { String s = 'hello'; } } } Duplicate variable: s Conversely, the ...


1

So, after renaming the folder into "C:\Tools\SalesforceCLI\bin" and modifying a path environment variable I was able to resolve the issue.


1

I hope you have installed SFDX from the link provided by Peter. If the problem still comes then it could be because you've forgotten to add the Path to System Environment Variable. If not, copy the Path "C:\Program Files\sfdx\bin" and paste it into System Environment Variable. This might solve your issue.


1

Here's the link for download SFDX: https://developer.salesforce.com/tools/sfdxcli


1

When you open a CSV file in Excel and click on save, the "Yes" will save the file as CSV again and "No" will prompt you to save the file as XLSX. Excel does save on this "Yes" even though closing the file will prompt you to save again. Therefore, based on your description, you did save the CSV with Excel, and that will change the formatting of the file ...


1

Since you don't save your CSV file during your open/close trick, my assumption is that the CSV file stays bitwise identical and therefore consequently is not the reason for your problem at all. It looks more like one of these weird java issues (configuration, memory, etc) You should try the same on a different computer or in a VM. An other idea would be ...


1

The bottom line of the dialog also hints at this. They seem to suggest moving the force cli app directly into sublime's default path. I believe sublime reads the system path, so changing the Windows path to include the force-cli location should work for you. by @drakored


1

There is no error. The upload should work fine. You are getting the warning because the mapping for customObject__c ( which would be an optional field) hasn't been provided.


1

You don't need to specify key="sfdc.Id". If you have extracted *.csv with opportunities and have configured mapping *.sdl update operation should work. opportunityUpdateMap.sdl: NAME=Name ID=Id extract.csv: "ID","NAME" "00636000006FRAZAA4","Boston" "00636000006FRAtAAO","Washington" process-conf.xml: <property name="name" value="csvUpdateOpp"/> ...


1

I'm not sure if this is a bug or a feature, but regardless, I've filed an issue on your behalf. In summary, assuming this is a bug, it's because the field values are being padded by a minimum length specified in the source code (force/display.go, lines 362-365), which I fixed by specifying a minimum length of 0 in my patch. It looks like I'll need to tweak ...


1

The error message you received is not exclusive to the Force.com CLI, but it is due to the program attempting to access an invalid memory address or dereferencing a nil pointer and Go (the language the program is written in) throwing a runtime error. According to the screenshot in your post, you receive the following error message after attempting to run ...


1

There is a great blog post here about getting started with the force.com cli including install instructions for the MAC. For those using a Mac, go to https://force-cli.heroku.com and download the Mac version. All you get in your Downloads folder is a single file called "force". There is no installer, you just have to put this file someplace that ...


1

As Daniel Ballinger's answer and the comments point out, there was a bug in the force cli. But as of v0.23.0, there's a new --wait option for the bulk query command that let's avoid polling for the job to finish: $ force bulk --wait query CallRecord__c "select Account__c, CallFlow__c from CallRecord__c" | tee out.txt


Only top voted, non community-wiki answers of a minimum length are eligible