Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
Questions about second-generation packaging (2GP). Includes the partner-centric feature of Managed 2GP as well as the customer-centric feature of Unlocked Packages.
2
votes
1
answer
499
views
"Developer name already exists for custom metadata of this type" while pushing source to scr...
We have an internal (non app exchange) 2gp managed package. The source is composed of a main package and several supporting packages with protected custom metadata. …
2
votes
Accepted
"Developer name already exists for custom metadata of this type" while pushing source to scr...
This turned out to be pure user error. I found that duplicate copies of the same metadata row appeared in different parts of the source tree when I pulled from master. It was very obvious (and a bit …