So this is a weird scenario that I can't seem to find answers for. My team wants to push for the Salesforce DX Unlocked packaging strategy in a few months.
First off, its annoying because I have to create a trial org just to create test packages because I am told that once you create a DX package, you CANNOT delete a package or go down a version number. So our only way of testing out unlocked packages without pushing too many version numbers is to create a trial org.
The scratch orgs deploy with no problem now but when I deploy the same metadata project into an Unlocked Package in the trial org and create the new version, I get the following issue.
So we're using an "AccountsContactsRelation" object which is a standard object and NOT custom, but it only works when you enable the "ContactsToMultipleAccounts" feature, also in "Accounts" settings in the Setup menu. So when I deploy scratch orgs as usual, I need to put that feature to enable in the config file and it deploys without issues. But in a package, I have no way of doing such a thing.
Is this one of the many things that I cannot package? What if I have a package or another object's field dependent on this Object, will I still encounter errors or will it package OK without this object? Worst case scenario that it is not deployable in a package, will this object just reside regularly in the package and I can still be able to install this package alongside this and many other objects? Im sorry guys, yes I'm new to Salesforce in general. I picked up quite a bit the last few months but I have alot on the line here, I am a one man army as a contractor.
One thing I forgot to mention. When i create the package, I get the error below after running the package:version:create command “AccountContactRelation: invalid fullName, must end in a custom suffix ( for ex. __c )