[SalesForce] Deploying Lightning Pages to sandbox

[This] can be achieved by using the following in an applications/AppName.app metadata file:

<profileActionOverrides>
    <actionName>View</actionName>
    <content>PageName</content>
    <formFactor>Large</formFactor>
    <pageOrSobjectType>Account</pageOrSobjectType>
    <recordType>Account.RecordType</recordType>
    <type>Flexipage</type>
    <profile>ProfileName</profile>
</profileActionOverrides>

Courtesy of Stephen Titley, https://success.salesforce.com/ideaView?id=0873A000000cLetQAE

And also this article: Activate Lightning Record Page via Metadata API

The docs say "The only valid values are record-home and standard-home" for <pageOrSobjectType>. You can put an sObject in there; if you haven't sub-classed record type (you are using master) you can just remove the <recordType /> element.

The Metadata Coverage Report concerns whether a type is accessible with the Metadata API. The Unsupported Metadata Types will be those that are not accessible at all to the API.

As you noticed, there's still another consideration which is component access - the above applies to global metadata components whereas private components are not accessible to be retrieved or deployed.

I believe only the following types have this concept of user-defined components (ex. "private" or "my" folders) and you noted the major ones in your question:

• List View
• Reports
• Dashboards
• Email Templates
• Content Assets

Only the List Views Doc contains this note

List views with the Visible only to me Restrict Visibility option aren’t accessible in Metadata API. Each of these list views is associated with a particular user.

There's an old idea asking for ability to access Personal Reports through the Metadata API, but no ideas for any of the others I could find.

The above is an example of a limitation of the Metadata API and there's many others I won't be able to list. A good starting point is the Special Behavior in Metadata API Deployments as well as many ideas asking for specific limitations:

• Lightning Record Page activation should be available via Metadata API
• Enable Create/Delete of Country and State Picklists with Metadata API
• Activate/Deactivate Flows via Metadata API
• Add Service Presence Statuses Access to Metadata API
• Allow Named Credentials to be migrated without the Password

Another good way to figure out quirks is to look through the public knowledge bases' of CI/CD tools that work with the Metadata API closely and hit many of these issues in a wide range of features on the platform.

• Gearset
• Copado