SFDX - error on deploying changes related to big object

Issue #2028 resolved
Mateusz Bednarek created an issue

Hello, some time ago we switched from MetadataAPI to SFDX. The Project’s structure has been updated accordingly.

We have two big objects in our project, they both have indexes configured. The Index file comes from the repository, the structure looks like this:

Whenever I try to deploy anything (using either CMD+S or RMB>Illuminated Cloud>Deploy Metadata), if any Index file is present in the file tree, an error window pops up. This applies only to SFDX file structure, using Metadata API was not a case.

Error log from the idea.log file attached below:

DEBUG - atedcloud.util.CommandLineUtil - Returning command-line response: CommandLineResponse{exitCode=1, output='{  "status": 1,  "name": "SourcePathInvalid",  "message": "The sourcepath \"/Users/xxx/src/main/default/objects/XXX_Market_big__b/indexes/XXX_Index.index-meta.xml\" is not a valid source file path.",  "exitCode": 1,  "commandName": "SourceDeployCommand",  "stack": "SourcePathInvalid: The sourcepath \"/Users/xxx/src/main/default/objects/XXX_Market_big__b/indexes/XXX_Index.index-meta.xml\" is not a valid source file path.\n    at Function.create (/usr/local/lib/sfdx/node_modules/salesforce-alm/node_modules/@salesforce/core/lib/sfdxError.js:160:16)\n    at Object.exports.getSourceElementForFile (/usr/local/lib/sfdx/node_modules/salesforce-alm/dist/lib/source/sourceUtil.js:127:32)\n    at Object.exports.getSourceElementsFromSourcePath (/usr/local/lib/sfdx/node_modules/salesforce-alm/dist/lib/source/sourceUtil.js:155:39)\n    at async SourceDeployApi.doDeploy (/usr/local/lib/sfdx/node_modules/salesforce-alm/dist/lib/source/sourceDeployApi.js:58:43)\n    at async SourceDeployCommand.execLegacyCommand (/usr/local/lib/sfdx/node_modules/salesforce-alm/dist/ToolbeltCommand.js:149:29)\n    at async SourceDeployCommand.run (/usr/local/lib/sfdx/node_modules/salesforce-alm/dist/commands/force/source/deploy.js:32:16)\n    at async SourceDeployCommand._run (/usr/local/lib/sfdx/node_modules/@salesforce/command/lib/sfdxCommand.js:93:40)\n    at async Config.runCommand (/usr/local/lib/sfdx/node_modules/@oclif/config/lib/config.js:173:24)\n    at async Main.run (/usr/local/lib/sfdx/node_modules/@oclif/command/lib/main.js:27:9)\n    at async Main._run (/usr/local/lib/sfdx/node_modules/@oclif/command/lib/command.js:43:20)\n    at async Object.run (/usr/local/lib/sfdx/dist/cli.js:32:20)",  "warnings": []}', error='', duration=3010} 

The only workaround I found is to manually remove Index files from the file tree, then the deployment is successfully done.

Illuminated Cloud:

Version 2.2.0.0

Build 20211216095825

InteliJ:

Version 2021.2.3 (CE)

Build: #IC-212.5457.46

macOS BigSur ver. 11.6.1

Comments (6)

  1. Scott Wells repo owner

    Hi. What I'm seeing in this error is coming from the Salesforce CLI. You can almost certainly reproduce this behavior outside of IC2 by running the same command directly from the command line. The exact command that IC2 is running should be available in the debug log just above the provided excerpt. Assuming that's the case, you should log an issue in the CLI's public issue tracker. If you find that the same command does not fail from the command line but does from IC2, please add the full execution from the debug log so I can see what is occurring in more detail.

  2. Scott Wells repo owner

    I'm going to resolve this since it seems to be specific to the CLI. If you do find that you cannot reproduce it outside of IC2, feel free to reopen and I'll get additional diagnostic information from you.

  3. Log in to comment