How to control the default retrieve/pull destination folder in Illuminated Cloud when using multiple source paths?

[akippiko]

Hi,

I’m using Illuminated Cloud in a project where I have multiple source paths defined like this:

```
force-app/main/default 
force-app/main/other-app  
```

When I retrieve or pull metadata:
• If the metadata already exists under export-app, it updates correctly there.
• However, if the metadata does not yet exist in any local folder, it’s always downloaded into the default folder.

I know I can modify sfdx-project.json to change the "default": true package directory, but I’d like to know if there’s a simpler or more practical way to control where new metadata goes, especially when working within Illuminated Cloud.

[Scott Wells]

When retrieving (as opposed to pulling) metadata,  you can specify a default source root for newly-retrieved metadata via Illuminated Cloud | Configure Module. Note that the Default source root selector is only displayed when the module has more than one configured source root.

When pulling metadata, the Salesforce CLI uses the package directory set as default=true for newly-retrieved metadata. That's not controlled directly via IC but rather via sfdx-project.json.

Regards,

Scott Wells

[akippiko]

Thanks, that makes sense and works as expected.

However, I ran into a small issue when testing the Default source root setting.

When I set other-app as the default source root via Configure Module > Default source root, and then retrieved metadata (e.g., a layout), the retrieved path ended up like this:

```
force-app/main/other-app/main/layout/xxx
```

As you can see, it inserted an unexpected main subdirectory inside other-app, resulting in a nested path like other-app/main/layout instead of other-app/layout.

Is this expected behavior? Or is there something I might have misconfigured?

2025年8月1日金曜日 12:29:35 UTC+9 Scott Wells:

[Scott Wells]

No, that sounds like a bug. Do you mind logging it in the public issue tracker so that it's concretely on my radar? Should be pretty simple to address, I'd think.

Regards,

Scott Wells