'package version create' is failing for all Custom Metadata records with 'not found custommetadata__mdt'.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
The issue names the package version create command but provides no source files, tests, or reproducible codeset. Start by reproducing the failure with a minimal Custom Metadata package and inspect the package-version creation entry point; done means the command succeeds and the Custom Metadata records deploy without the reported errors.
Written by the indexing model from the issue text.
Description
Note
Before you submit your issue, make sure that:
- You're using the latest version of Salesforce CLI.
- You've searched both open and closed issues for related posts.
- You've used the
doctorcommand to diagnose common issues.- You understand that GitHub Issues don't adhere to any agreement or SLA.
- If you require immediate assistance, use official channels such as Salesforce Customer Support.
Summary
When I create package version, I met the messages something like followings.
It is similar problem like Issue #1582
MyCustom__mdt: Must specify a non-empty plural label for the CustomObject
MyCustom__mdt: My Custom Layout: Parent entity failed to deploy
MyCustom.RecordName: Custom metadata type MyCustom__mdt is not available in this organization.
MyHandleTriggerHandler: Invalid type: MyCustom__mdt
Steps To Reproduce
I cannot provide the codeset, it is company confidentials.
However, I was create a package version at 2024/11/25 with cli version 2.66.7. But it was failed at 2024/11/26 with cli version 2.66.7 and 2.67.7. I trying to package version create with almost same codeset. I just chaged a field size of string field of custom metadata. If I tried to restore the field to previous one, package version create still failed.
I also tried with version 2.68.6 right now, met the same result 'failed'
Expected result
Package version cretaed
Actual result
Failed package version create.
Additional information
System Information
OS : Windows 10
Terminal : PowerShell in VS Code
{
"architecture": "win32-x64",
"cliVersion": "@salesforce/cli/2.68.6",
"nodeVersion": "node-v22.11.0",
"osVersion": "Windows_NT 10.0.19045",
"rootPath": "C:\\Util\\sf\\client",
"shell": "powershell",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.2.10 (core)",
"@oclif/plugin-commands 4.1.10 (core)",
"@oclif/plugin-help 6.2.18 (core)",
"@oclif/plugin-not-found 3.2.28 (core)",
"@oclif/plugin-plugins 5.4.17 (core)",
"@oclif/plugin-search 1.2.16 (core)",
"@oclif/plugin-update 4.6.13 (core)",
"@oclif/plugin-version 2.2.16 (core)",
"@oclif/plugin-warn-if-update-available 3.1.23 (core)",
"@oclif/plugin-which 3.2.19 (core)",
"@salesforce/cli 2.68.6 (core)",
"apex 3.6.3 (core)",
"api 1.3.2 (core)",
"auth 3.6.75 (core)",
"data 3.11.4 (core)",
"deploy-retrieve 3.15.13 (core)",
"info 3.4.21 (core)",
"limits 3.3.40 (core)",
"marketplace 1.3.6 (core)",
"org 5.2.4 (core)",
"packaging 2.9.3 (core)",
"schema 3.3.42 (core)",
"settings 2.4.6 (core)",
"sobject 1.4.46 (core)",
"telemetry 3.6.23 (core)",
"templates 56.3.30 (core)",
"trust 3.7.43 (core)",
"user 3.6.3 (core)"
]
}
- Dominant language
- No language data
- Stars
- 571
- Forks
- 80
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from forcedotcom/cli
-
investigating validated
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
forcedotcom/cli#3657 · 2 comments ·
-
area:afdx owned by another team
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
forcedotcom/cli#3645 · 2 comments ·
-
bug investigating validated
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
forcedotcom/cli#3644 · 6 comments ·
-
area:afdx bug investigating owned by another team validated
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
forcedotcom/cli#3625 · 4 comments ·
-
area:afdx bug owned by another team
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
forcedotcom/cli#3608 · 2 comments ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EverMind-AI/Raven#845 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aoqia194/leaf-loader#19 ·
-
good first issue hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
RogueAlg0/taken#385 · 3 comments ·
Maintainers usually reply within 1 day
-
discover: `sudo RTK_DISABLED=$VAR …` is not detected as a bypass when `sudo` is a transparent prefixOpenarea:cli bug good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
filamentphp/filament#20630 ·
Maintainers usually reply within 1 day