7

With the introduction of SFDX, we also got a new representation for the metadata/code known as "Source form". This is different from the traditional representation, which is called "Metadata API form" Source form is meant to be more flexible for project structure in versioning systems (git, subversion, etc...) and is also important for driving the pushing ...


4

I have never tried it but as mentioned in documentation, you can only clone sandboxes of similar license types. As a best practice, I would recommend you store all the metadata and customization logic to a Version control system and treat it as source of truth. A cloned sandbox uses the same license type as its source org. For example, to clone a Full ...


2

In case anyone is following this: Dependency API is now (Spring '20) available in all environments including production orgs.


2

There are a few options and some pros/ cons. This is not an exhaustive list so ask away to discuss more. Disclaimer: I work for Snapshot, one of the tools that I discuss below. Here goes: Unmanaged packages: Just go to create package through Setup. Setup > Build > Create > Packages in Classic, Setup > Platforms Tools > Apps > Packaging > Package Manager ...


1

I would recommend using a vendor DevOps tool such as Gearset. You can copy metadata from any org to any org, regardless of sandbox type (and even copy data) These vendor tools have visual user interfaces (no command line) and easy for admins and developers to quickly grasp. Source control is supported as a source and target as well. Disclaimer: I'm not an ...


1

You can retrieve the managed content type by adding ManagedContentType as a type in package.xml Sample example <?xml version="1.0" encoding="UTF-8"?> <Package xmlns="http://soap.sforce.com/2006/04/metadata"> <types> <members>*</members> <name>ManagedContentType</name> </types> <...


1

There's a metadata type available as of 46.0 called MutingPermissionSet that you need to retrieve as well.


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.


Only top voted, non community-wiki answers of a minimum length are eligible