-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom Labels deployment doesn't work #652
Comments
Let's use #673 to track this. I added a partial fix for custom labels in the current release candidate. Can you try installing that to see if it unblocks you? It's a partial fix because it converts/deploys all custom labels in the project versus just the labels defined in the manifest. Converting/deploying specific labels is coming soon. |
@shetzel |
@IvanLevytskyiDataArt - thanks for confirming! |
Summary
Custom Labels deployment doesn't work
Steps To Reproduce:
sfdx force:source:deploy --manifest manifest/package.xml -u %1 -l NoTestRun
Expected result
Custom label must be created on specified org.
Actual result
It doesn't create any custom labels.
Additional information
SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
sfdx-cli/7.75.0-5521f40d11 win32-x64 node-v12.18.3
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)
@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.0 (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.8 (core)
generator 1.1.3 (core)
salesforcedx 49.13.0 (core)
├─ templates 49.9.1 (core)
├─ @salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
├─ custom-metadata 1.0.10 (core)
├─ salesforce-alm 49.12.1 (core)
└─ apex 0.1.0 (core)
sfdx-cli 7.75.0 (core)
OS and version:
Windows 10 Enterprise
The text was updated successfully, but these errors were encountered: