"Regular" (Developer Edition) scratch orgs don't have the same feature set as Enterprise Edition orgs, or any arbitrary org. Packaging orgs often have a lot of features turned off, as well, to avoid inadvertent dependencies.
That makes pulling Profile metadata out of a scratch org for deployment to a non-scratch org... difficult, in many cases, and Data.com ...
The way I use to update custom metadata in Apex is via the Andrew Fawcett Github (unmanaged) Custom Metadata Services
Custom Metadata Services (CMS) is a small library created to wrap the native Apex Metadata API to leverage the native SObject types for custom metadata in a more DML orientated way. It also aims to simplify the handling of the async ...
I use two things:
Use .forceignore for quite a lot e.g.
# List files or directories below to ignore them when running force:source:push, force:source:pull, and force:source:status
# More information: https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_exclude_source.htm
# LWC configuration ...
First, is this a good approach?
Maybe, but I'm pretty skeptical. Can you define the business case for needing over 200 custom Contact fields on your Lead object? Surely your web-to-lead forms won't be capturing data for anywhere near that many fields. Why not surgically define specific fields you wish to capture via web-to-lead and build only that (...
Out of the box - no. Metadata deployments are tracked via an Id.
You can create custom object(s) and custom screen(s) to manage a metadata deployment. For example, one custom object could map the deployment Id to your custom deployment name.
Yes. When you deploy metadata via deploy(), there's a performRetrieve flag that when set to true allows you to ...
The Metadata API does not support queries. You would have to iterate through the returned metadata and filter it manually via Apex logic.
The Metadata API RetrieveResult does include FileProperties entries, with the values lastModifiedById, lastModifiedByName, and lastModifiedByDate.
While the Tooling API allows queries, many Tooling API objects don't ...
You can use MetadataService.cls to get all this info. For example, you can check method readCustomObject() in https://github.com/financialforcedev/apex-mdapi/blob/master/apex-mdapi/src/classes/MetadataServiceExamples.cls. to get all the objects info.
Source : https://github.com/financialforcedev/apex-mdapi
As mentioned before - get the list of Global Actions with:
But you can update the settings by defining each quickAction.
The key is you don't have to name each Object before the quickAction name.