6
You should read through the documentation on force:source:deploy again
The reason why you're only validating the changes is because that's exactly what you're telling sfdx to do when you use the -c flag
-c | --checkonly
Optional
Validates the deployed metadata and runs all Apex tests, but prevents the deployment from being saved to the org.
...
4
If you use -c , note that the command will just validate it.
I suggest you use the Visualstudio For Salesforce extension and deploy using the deploy to source option as shown below
If you are using CLI then you have to add all the metadata and be specific in format as shown below and it will be tedious exercise instead just deploy by clicking on the path.
...
4
Spring '20 release notes are mentioning increased speed when uploading a change set.
4
You should Disable Caching. This has obvious performance penalties, but should show the latest version of your code.
From Setup, enter Session in the Quick Find box, and then select Session Settings.
Deselect the checkbox for “Enable secure and persistent browser caching to improve performance”.
Click Save.
2
Protected Custom Metadata Types are not visible in the subscriber org:
When a custom metadata type is package-level protected using 2GP, records are only accessible from code within that managed package. Also the subscriber, and other packages, even within the same namespace, can’t access the custom metadata type or its records.
That's the intended ...
1
I believe the issue is in your package.xml. When you reference the Custom Metadata type in Custom object, you utilize __mdt
However, when you reference records of a Custom Metadata Type, you do not include __mdt.
This is mentioned in the Metadata API documentation for Custom Metadata
If you change your package.xml to this, it should appropriately bring ...
1
This is due to the picklist value that is being used in this WorkflowFieldUpdate is not present in the Target org. Make sure to include the Field being updated in the package OR make sure that the picklist value exists in the Target org.
1
For your 2GP packages, you need to use the name/versionNumber format for your dependencies:
"dependencies": [
{
"package": "ParentPackage",
"versionNumber": "0.1.0.LATEST"
}
]
It took me a little while to figure this out myself.
Also, make sure you do not have an object-meta.xml file in the root of each object folder for the child ...
1
A slight work around for this is to add a class with a static method to the unmanaged package and then run the method anonymously in the developer console post install...
public class MyUnmanagedPackagePostInstallScript {
public static void doSomething() {
//I do things like create records and dml
}
}
Install the package with the class ...
1
Four years later, Salesforce DX and Unlocked Packages have reversed the answer given above. Now Salesforce is recommending that application development takes place in Unlocked Packages and that these can be installed in Production or a Sandbox for many of the reasons that the original post mentions. Existing applications should be rebuilt as Unlocked ...
Only top voted, non community-wiki answers of a minimum length are eligible
