5

Is there a standardized approach or automated process for making a Scratch-Org look exactly like your Production Environment (Metadata/Packages/etc.)? force:org:shape and force:org:snapshot are in pilot, so eventually there will be automated support. However, this does not help you right now if you're not already in the pilot programs. This means you'd have ...


3

Basically, you can't. At a per-field level, the field's metadata must be fully formed and correct. The documentation states: You must supply values for all the required fields in the component.


3

Use the Tooling API to query CustomTab. In the Developer Console, go to the Query Editor, then write a query, and check the Tooling API box at the bottom of the tab. You can start with this query. Check the docs for more info. Select CreatedDate, CreatedById, DeveloperName From CustomTab


3

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 ...


3

[edited based on @Derek F's comments] Reports are located in three places that control visibility: Public: the report's ownerId is the Organization; anyone can view Shared (my label): the report's ownerId is a shareable Folder Private: the report's ownerId is the user's Id; only the user can view Public and Shared reports are accessible with the Metadata ...


2

I think the second problem you listed is causing the first problem, and unfortunately it's a bit of a layered answer. I'm also assuming that the MetadataService layer you've generated is all correct. The first part to solve is getting the ConnectedAppOauthConfig.isAdminApproved = true. Now I couldn't get this to set on creation of the Connected App. However,...


2

Taking the summary out of comments for everyone's benefit: the screens you reference are for implementation of a scenario where an external service/app is acting as a SAML identity provider, SF is a service provider. SamlSsoConfig is the metadata object that corresponds to the Single Sign-On Settings screen, it captures a configuration of the (external) ...


1

You cannot automate the enablement/config of a built-in identity provider via APIs. The APIs do not exist for doing so. The likely reason for non-existence of APIs is security + change management. Enabling the identity provider significantly changes the security posture of the org and while it might be a safe change, it's a type of change that should be done ...


1

How about using UI Api to get listViews? /services/data/v46.0/ui-api/list-records/Account/AllAccounts https://developer.salesforce.com/docs/atlas.en-us.uiapi.meta/uiapi/ui_api_resources_list_views_md.htm?search_text=list%20view


1

The problematic references appear to be in the Account Record Types Broker, Cedent, Other, and Reinsurer. Those record types include references to picklist values that are not being migrated, presumably because your package.xml doesn't include StandardValueSet metadata for Account.Type. Altering the Type field itself in your source org won't fix the problem ...


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