Cli: sfdx force:source:deploy is not deploying the custom fields.

[ar-srinivas]

Summary

sfdx force:source:deploy is not deploying the custom fields and skipping custom fields when bundled with any other metadata.

Steps To Reproduce:

Repository to reproduce: https://github.com/ar-srinivas/SFDX_CustomFields.git
Branch: Dev

1. Clone the "Dev" branch source
2. Run the following command from source folder. sfdx force:source:deploy -x package.xml -u --apiversion=49.0 -w 0 --json

Expected result

The two custom fields from the source structure should be deployed to the target org. CLI should return deployment ID and status. The behavior should remain same when we pass -x package.xml or -m "CustomField"

Actual result

Result is shown as below

{
"status": 0,
"result": {
"outboundFiles": [],
"deploys": []
}
}

Additional information

It is failing to deploy custom fields when I add -x package.xml but when I replace it with -m "CustomField" the deployment is processed succesfuly.

Also skipping the custom fields when included any other metadata.

SFDX CLI Version(to find the version of the CLI engine run sfdx --version): sfdx-cli/7.74.1-32db2396ed win32-x64 node-v12.18.3

SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)

OS and version: Windows 10

[shetzel]

This is actively being worked on and the fix will be included in the next patch release.

[nabondance]

Until the patch is released (Oct. 1st), a working workaround is to change the salesforcedx version using:
sfdx plugins:install [email protected]

Special thanks to @alanjaouen

[engineerakki]

Is this fixed ?
I dont want to change salesforcedx version.
I am still getting the same issue

[vnehess]

I have encountered this in my development as well, the problem: not creating custom fields, seems to follow the latest cli version - 7.75.0
earlier versions always created the fields, I was using 7.63.0.

[FinnArild]

I can also confirm this issue in versions 7.75.0 and 7.75.1

[akashpunera]

This issue is still not resolved, facing this in 7.75.0 as well

[1ktribble]

7.75.1 - when deploying a new custom field alongside a new dependent picklist, the dependent picklist fails to deploy.

Error: In field: controllingField - no CustomField named field_name__c found

Both fields are in the object in the package.xml file. This occurs with both the source:deploy and mdapi:deploy commands.

[girasedinesh]

I am also facing the same issue from last two weeks. I have 8 new custom fields from one object, added them in package.xml, but it deployed only first field from the list. Even i tried adding CustomObject section in the package.xml, but result is still same. This is happening on production instance, its working fine on sandboxes though.

[shetzel]

@girasedinesh
If the output of sfdx plugins --core doesn't match this then you probably don't have the fix. The code works the same regardless of production versus sandbox versus scratch org.
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.2.0 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.9.1 (core)
@oclif/plugin-update 1.3.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.4.3 (core)
alias 1.1.2 (core)
analytics 1.12.1 (core)
config 1.1.9 (core)
generator 1.1.3 (core)
salesforcedx 50.1.1 (core)
├─ apex 0.1.1 (core)
├─ custom-metadata 1.0.10 (core)
├─ templates 50.1.0 (core)
├─ @salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
└─ salesforce-alm 50.1.1 (core)
sfdx-cli 7.76.1 (core)

If your plugins match this then provide steps to reproduce since it's working properly for me and others.

[girasedinesh]

This is what i am getting
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.2.0 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.9.1 (core)
@oclif/plugin-update 1.3.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.4.3 (core)
alias 1.1.2 (core)
analytics 1.12.1 (core)
config 1.1.9 (core)
generator 1.1.3 (core)
salesforcedx 50.1.1 (core)
├─ templates 50.1.0 (core)
├─ @salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
├─ custom-metadata 1.0.10 (core)
├─ salesforce-alm 50.1.1 (core)
└─ apex 0.1.1 (core)
sfdx-cli 7.76.1 (core)

[girasedinesh]

I am using similar package.xml in the manifest folder for deployment
"


SomeCustomObject__c.Field1__c
SomeCustomObject__c.Field2__c
SomeCustomObject__c.Field3__c
SomeCustomObject__c.Field4__c
SomeCustomObject__c.Field5__c
CustomField

49.0
"

[girasedinesh]

[shetzel]

@girasedinesh - I would try uninstalling the CLI and reinstalling to the latest.

[girasedinesh]

Its resolved now. Docker image from our yml file was not picking the latest version, now it started picking the latest version. Thanks all for your valuable suggestions.

[shetzel]

@girasedinesh - Glad you got it working! 👍

[ravishankar-peri]

I see the same problem with Workflow* types.

[jitendrabhagatdevops]

@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.2.0 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.9.1 (core)
@oclif/plugin-update 1.3.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.4.3 (core)
alias 1.1.2 (core)
analytics 1.12.1 (core)
config 1.1.9 (core)
generator 1.1.3 (core)
salesforcedx 50.1.1 (core)
├─ apex 0.1.4 (core)
├─ custom-metadata 1.0.10 (core)
├─ templates 50.1.0 (core)
├─ @salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
└─ salesforce-alm 50.1.1 (core)
sfdx-cli 7.82.1-0 (core)

I have this , still I am not able to deploy the custom field, is this bug RESOLVED in this version of SFDX - sfdx-cli 7.82.1-0

[shetzel]

@jitendrabhagatdevops - I don't know how you have salesforcedx 50.1.1 (core) with sfdx-cli 7.82.1 (core) but that is the problem. You should be on version 50.7.1 of the salesforcedx plugin. Please run sfdx update