It is straight forward steps to move your Dynamo template file from one organization to another. However, users tend to face errors or the template doesn't work in Production as it did in Sandbox. The most comment problem that causes error in the template after deploying in Production is having different data structure between the two organizations or some part of the template still contains the old information taken from Sandbox. Follow the checklist below to avoid the errors.
Before moving template to Production
1. Ensure the similarity in data structure
Make sure that your Sandbox and Production (or the old and the new organization) have the same data model. If you have changed anything in your Sandbox before or during the creation of the template, update your Production org first.
In case your Sandbox is very different than the Production due to under development project or different testing purposes, the Production org needs to have at least all the fields used in the templates, such as
- Fields in the template layout to get dynamic data from the CRM into the documents. For example: Heading of the document = "1.
<Account.Name>" - Fields used as conditions to trigger the change of the content in the documents. For example: Hide the discount column in pricing table when the field
<Hide_discount__c>in Salesforce is checked - Fields used in the template's logic or setting. For example: When end-user select the "Save" button, upload the outcome document in Salesforce with name "Offer for
<Account.Name>_ Offer ID<Opportunity.Offer_ID__c>" - Fields and record types which are used in the Custom Buttons and Links or the Visualforce Page
If you use custom fields in the template, make sure those fields have the same API name in Sandbox and Production
2. Check the Attachments or Imported documents
If your template has attachments or imported documents, make sure you have those available in the Production org as well. In the template, you can indicate which files from Salesforce to be attached, by pointing at either the file's Title or Content Document ID. As the IDs are different in in Sandbox and Production, you will need to update the template with the correct ID. Updating ID can be done after moving the template to Production. It's good to have an overview of wherein the templates those IDs are used before the move and prepare the Production org accordingly.
- Content Document ID: You will need to change the correct Content Document IDs in the template's tags.
- Content Title: If you use the file's Tilte in the template, make sure all the files in Production have the exact Title
- Library ID: If you have all the attachments in a specific Salesforce Library, you need to update the template with the Library ID in Production
3. Ensure users have the right permissions
End-users will need certain permission in Salesforce in order to use Dynamo. Make sure all the permissions are set up properly for end-users when preparing your Production org.
- API Enabled: How to enable API in Salesforce
- Pre- authorize Dynamo in Connected Apps (for using Dynamo with Lightning Experience)
- Visibility of those fields used in the templates.
- Access at least as Viewer to the Libraries or Chatter Groups those contain the attachment and template files. How to manage Dynamo template files in Salesforce
- Access at least as Author to the Libraries or Chatter Groups those will store the outcome documents or have the permission to Upload Files into the record.
Move template to Production
1. Ms Office template
Open the template from sandbox (in Office, use Dynamo’s Open button)
In Dynamo Office add-in, in Dynamo ribbon, click Document
Click Show Embedded Info
From the drop-down, select Remove Repository Information and click Remove (this removes the template’s connection to the sandbox)
In the Confirm pop-up, click Yes
Click Close, and OK to close all the pop-up windows
Change your account to production from Account button
Use Dynamo’s Save As to save the template in production
2. Online template
Export the template to your computer
Log out from your Online Editor
Log in again to the Online Editor with your Production org credential
Import the *.dap file from your computer
Make change if needed
Save as a new file
Test template in Production
Ensure the URL in Custom Buttons and Links or Visualforce Page is updated, especially if there is any parameter with ID values
If there is error, double check the points mentioned in "Before moving template to Production"
Comments
0 comments