Is it possible to deploy a Validation rule from a custom object?
We've been able to do the same kind of validation rule deployment from Standard Objects without issue. I got it to work by deploying the entire Custom Object (which picks up all fields, rules, etc.), which was fine in this case. However, there may be times where we do not wish to deploy the entire object.
Is it possible to deploy a custom object in two locations?
Trying to deploy gives the "Must specify a non-empty label for the CustomObject". Copying MyObject__c.object-meta.xml from MyPackage to the happy soup lets it deploy successfully, but obviously having our source in 2 locations is no an option.
Why am I getting a non-empty label error with my metadata?
If you specify the entire custom object in your package, then you will get the non-empty label error. If you're getting this via Heroku/DX, probably happening because you pasted metadata directly into force-app/main/default instead of using sfdx force:mdapi:convert --rootdir <directoryName>.
Why does the customobject wildcard fail to deploy?
If you only have the CustomObject wildcard in the manifest it fails in the same way (because it needs the fullname in the manifest). The wildcard does not care about folder names. The error is because you're deploying the packaged CustomObjects (i.e., the objects in package/main/default/objects/*) along with unpackaged metadata.
Summary
Custom Fields on objects that reside in packages (both managed & unmanaged/unlocked) fail to deploy, requiring an object-meta.xml file that already exists in the package.
Steps To Reproduce
I'm sorry but I don't know if I have the ability to create an easy reproduction. I think that would require creating an unlocked package & then unpackaged source..... This is most certainly a confirmed issue though.
Actual result
Get the error: "Get "Error:Must specify a non-empty label for the CustomObject""
github-actions bot commented on Oct 5, 2021
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.
mshanemc commented on Oct 5, 2021
please uninstall salesforcedx and try it again! You're missing out on all kinds of new fixes.
keirbowden commented on Oct 21, 2021
I'm seeing this since I updated my CLI last night. I'm developing a 2GP extension to a 1GP package. I have a bunch of stuff around the 1GP package that I need to get the code to push in an unpackagedMetadata` directory.
WillieRuemmele commented on Oct 26, 2021
Hi @jonnypetraglia sorry for the delayed response. I'm just confirming, before digging in too much more, that if you upgrade to >7.122 like Keir did above is this issue still present?
