Scratch Connections Not Selectable for Project

[Tyler Russell]

Apologies if I missed this somewhere or have a fundamental misunderstanding of how things work, but I couldn't find any documentation on behavior that I'm seeing.

I'm working to setup a test project. My org list from sf shows that I have a DevHub and multiple scratch connections.

The connections also correctly show in the Illuminated Cloud application configuration.

And in the list of connections in the "Open Connection" dialog.

However, the scratch orgs don't show up as valid options in the Project Configuration.

Or as a selectable connection in the Deploy modal.

Based on behavior, it looks like the synchronize and deploy options are evaluating against the DevHub org not against the default scratch org as specified in sf? That makes sense based on the selected connection, but if that's the case, how do I select the scratch org as a connection? I am assuming the Cloud Illuminated deploy mimics the sf project deploy start command, which has the --target-org flag? If so, how am I supposed to be specifying that?

Is there a conceptual difference between project and global connections (as labelled in the connection dropdowns) that I'm missing?

Again, my apologies if I'm barking up the wrong tree here. I wasn't sure if it was a bug or simply a lack of knowledge on my part. 

Thanks for any help.

[Tyler Russell]

My apologies, the inline screenshots didn't appear to come through. Here they are for any future reference.

sf org list

Open connection dialog

Project configuration

Deployment modal

Thanks again.

[Scott]

Apologies but your images aren't coming through in your post. I'll answer as best I can, though.

First, all connections that you configure as global connections. Once a connection has been associated with a module in the current project (most Salesforce projects likely have a single module), it becomes a project connection as well. You can find more information about setting up connections and associating them with projects in the user guide:

https://bitbucket.org/RoseSilverSoftware/illuminatedcloud/wiki/User_Guide/Home

Scratch org connections are available for all project types, but they're only visible in metadata format (i.e., pre-Salesforce DX) projects if they're configured to use raw deploy/retrieve/delete instead of source-tracking since those projects don't support source-tracking operations. So if your Salesforce project doesn't have an sfdx-project.json file in the root directory, it's considered metadata format. If you want to use a scratch org with that project, check that option in the connection properties and it should become available for selection.

I'll stop there and see whether that helps or not. If not, please provide more information either here or via email and I'll be happy to help further.

Regards,

Scott Wells

[Tyler Russell]

>So if your Salesforce project doesn't have an sfdx-project.json file in the root directory, it's considered metadata format

That appears to have been the magic ticket.  My test project is a SFDX project (just their default project), but it was in a sub-directory of a monorepo. The IntelliJ project root was the base of the monorepo, not the SFDX project. I had followed the steps for importing from existing files (as documented here https://bitbucket.org/RoseSilverSoftware/illuminatedcloud/wiki/User_Guide/Create_Project_Files.md), but selected the root of the mono repo because we have multiple Salesforce projects.

Opening the test project subdirectory as a standalone new project (instead of being part of the parent) appears to have resolved the issue. I'm sure I could have configured the module as part of the monorepo project, but this is fine for now.

Thanks for the help!