6

The flow can be invoked from a user-facing process. Here are the parameters: /services/auth/xds/{org_id}/{authprovider_developer_name} - this issues the logout, &startURL=/0XA... - this ID tells SF which Named Credential to link the grant against, &scope=full... - list of scopes/privileges presented to the user at the Allow screen, Apex code to ...


4

You can retrieve DX-compatible formatted source using DX: sfdx force:source:retrieve -u prod-login -m "CustomObject:Account,CustomObject:Case,Profile" This should retrieve all the metadata you're asking for without the need for a package.xml, which you can then immediately turn around and push: sfdx force:source:push -u scratch-org-login You'll need to ...


3

This is the purpose of Salesforce DX. The folders won't be on the Salesforce server, but you will be able to organize your folders/packages in a repo. See the DX Falcon Template for an example. Yes, it will take time to convert and organize your source code, but the sooner you get started, the sooner you'll be able to take advantage of this feature.


3

If all you need to do is to kick off the oAuth flow so that the user may authorize the app, the auth provider supports this natively: public PageReference (String authProvider) { AuthProvider provider = [ SELECT Id,OauthKickoffUrl FROM AuthProvider WHERE DeveloperName = :authProvider ]; return ...


2

You can retrieve it with "workflowAlert" metadatatype. You can find more info at this URL here Workflow Metadata Ref, you might want to scroll through to the section "WorkflowAlert" to see field references associated to it.


2

In the given particular scenario, issue might occur due to duplicate values in picklist value set for chosen field. In case if field is retrieved by MetadataService, it already contains existing active value set definitions (as fieldMdApi.valueSet.valueSetDefinition.value). Since salesforce does not allow to have duplicate picklist values, there are no ...


2

Usual disclaimer: I work at Gearset. You can use Gearset's free trial to do this in a couple of minutes. Just log in and create a comparison between the org in question and a scratch org, then you can either deploy those objects straight to the scratch org, or you can download the zip package of the deployment that Gearset builds, which includes the ...


2

As of Summer '19 (v46.0), the INVALID_OPERATION errors you were hitting are no longer an issue! force:source:deploy now works when deploying to production. See an example below: sfdx force:source:deploy -m ApexClass:MyApexClass -l RunSpecifiedTests -r MyApexClass_Test -w 3 -u MyProductionOrg


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