This process is designed for the Production Org to be the hub, and manage copying from/to a Sandbox from/to Production.
For this reason, you require an integration user in your Sandbox with access to all the BUs you want to copy to/from, and has access to the Metadata API, so we also suggest ensuring this integrating user has the Account Engagement User Permission Set applied.
Additionally, you need to perform the following steps:
1. Install the latest Account Engagement Package.
2. Authentication:
Step 1: Create an External Client App in the Sandbox Org.
Step 2: Update Auth Provider in Production Org.
Step 3: Account Engagement API Named Credential
Step 4: Salesforce Metadata API Named Credential
3. Test & Setup:
Step 1: Test the Flow.
Step 2: Add the Flow to a Lightning Page of Choice.
To connect to another Salesforce Org (i.e. sandbox or production), you need to authenticate into that Org and enable access to the Salesforce Metadata API & Account Engagement API. Following are the steps to authenticate Production to the Sandbox:
Step 1: Create the Connected App in the Sandbox Org:
The Connected App provides the interface to authenticate into an org. To create the connected app:
1. In your Sandbox Org, navigate to Salesforce Setup > Apps > App Manager, and then click the New External Client App button.
2. Configure the External Client App as follows:
a. External Client App Name: Give it a suitable name for the integration. You need this in Step 2.
Recommend: Include MCAE Production or MCAE Sandbox in the name to make it easy to distinguish which environment you are connecting to.
b. Contact Email: Email Address of the admin who will be managing the sandbox-to-production promotion process.
c. Enable OAuth Settings: Checked
d. Callback URL: Source org’s auth provider’s callback URL
* Go to Source Org > Setup > Auth. Providers > Sandbox Asset Flow Auth > Salesforce Configuration > Callback URL.
e. Selected OAuth Scopes:
* Manage user data via APIs (api)
* Manage user data via Web browsers (web)
* Perform requests at any time (refresh token, offline_ access)
* Access unique user identifiers (openid)
* Manage Pardot services (pardot_api)
* Access the Salesforce API Platform (sfap api)
f. Uncheck the Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows checkbox.
g. Require Secret for Web Server Flow: checked
h. Require Secret for Refresh Token Flow: checked
3. Click Create.
Note: *It might take 10-15 minutes for the app to be ready for authentication.
*Recommend collecting your Consumer Key and secret for the next step.
Step 2: Update Auth Provider in Production Org:
The provided Auth Provider is configured to handle the authentication process.
To finish configuring the Auth. Provider:
1. In Production, navigate to Salesforce Setup > Auth. Providers and edit Sandbox Asset Flow Auth
2. Update the Consumer Key and Consumer Secret from the external app that was just created.
a. Go to Destination org > Setup > External Client App Manager > select the app that was created > Settings tab > Consumer Key and Consumer Secret
3. Click Save.
Step 3: Account Engagement API Named Credential
This named credential establishes access via an integration user to the Account Engagement API. Setup is as follows:
1. In your production org, navigate to Salesforce Setup, Named Credentials, and then select New Legacy.
* Be sure to select New Legacy and not New.
2. Configure the Named Credential as Follows:
* Label/Name: Pick an applicable name, e.g. MCAE API Access.
* URL: https://pi.demo.pardot.com
* Identity Type: Named Principle
* Authentication Protocol: OAuth 2.0
* Authentication Provider: Sandbox Asset Flow Auth
* Scope: pardot_api refresh_token
* Start Authentication Flow on Save: Checked
* Generate Authorization Headers: Checked
3. Click Save.
4. Login using the integration users credentials.
Step 4: Salesforce Metadata API Named Credential
This named credential establishes access via an integration user to the Metadata API to retrieve BU details. Setup is as follows:
1. In your production org, navigate to Salesforce Setup, Named Credentials, and then select New Legacy.
* Be sure to select New Legacy and not New.
2. Configure the Named Credential as Follows:
* Label/Name: Pick an applicable name, e.g. Metadata API Access.
* URL: https://mydomain--sandboxname.sandbox.my.salesforce.com
* Replace mydomain & sandboxname with the correct values for your org.
* Identity Type: Named Principle
* Authentication Protocol: OAuth 2.0
* Authentication Provider: Sandbox Asset Flow Auth
* Scope: api refresh_token
* Start Authentication Flow on Save: Checked
* Generate Authorization Headers: Checked
3. Click Save.
4. Login using the integration users credentials.
Congrats! You are now done with Authentication.
---
Next, run a test to validate that everything is authenticated. Following are the instructions:
1. In your Production org open Setup, in the Quick Find box, enter Flow.
2. Under Process Automations, select Flows.
3. Click Account Engagement Sandbox-Production Bulk Asset Copy Flow.
4. From the Flow Builder, click Run.
5. Follow the Flow UI Instructions.
Note: The first page asks you to select the named credential for Account Engagement Access and Metadata Access. Select the Named Credentials you created.
Finally, once tested, add the Flow Lightning component to a Campaign page, or any page of choice, see Add a Flow to a Lightning Page.
Tip:
If you don’t want users to select Named Credentials, copy the flow and modify it to set the Named Credentials as flow default variables vs. as screen-flow input.
000396734

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.