SharePoint Integration
The Microsoft SharePoint integration is a two-way integration with SharePoint online. It allows saving files to Sharepoint and loading files from Sharepoint.
The Sharepoint integration requires an additional feature license.
Use cases
From Salesforce to Sharepoint: SharePoint integration can be used to save files (e.g. generated documents) directly to SharePoint instead of Salesforce.
From Sharepoint to Salesforce: The integration can also be used to load files from SharePoint. The file could be e.g. an Office content template, an Office clause or a PDF attachment.
The Sharepoint integration has the following key benefits:
Savings on Salesforce storage cost - save your generated documents directly in Sharepoint instead of Salesforce to reduce storage on Salesforce. You can add a link to your Salesforce record pointing to the Sharepoint location so you keep track of where the file is.
Enrich your Sharepoint folder structure - If your company prefers to maintain a neat and organized file structure in SharePoint, integrating with Salesforce allows you to direct generated documents to the appropriate locations within SharePoint.
Load content to your document directly from Sharepoint - you can merge content from Sharepoint to your generated document such as Terms and Conditions to a generated Offer document. You can also load attachments; perhaps your Offer needs to go out to the customer with a Powerpoint document attached to the email? You can load the Powerpoint directly from Sharepoint.
Easy template management - if you are using Office output templates, you can edit and manage your templates directly from Sharepoint without going throug Salesforce. If you use Word clauses, you can also manage them directly from Sharepoint. This means that anyone having access to Sharepoint can manage your templates and clauses, no Salesforce license needed.
Convert DOCX documents to PDF from SharePoint: DOCX documents can be converted to PDF while being loaded from SharePoint. This means that your team can edit Word documents using Microsoft 365 and send the converted PDFs to customers from Salesforce with a click of a button.
Want to see the above magic in action? https://documill.com/book-a-demo/ with our experts to find out.
Prerequisites
The Dynamo feature license is enabled for the Salesforce org ID (production or sandbox).
A single integration user has been provided and authenticated through the dynamo-users.documill.com site.
A SharePoint site exists, and the integration user is a member of that site.
Adding an integration user
An integration user can be added through the dynamo-users.documill.com site.
Select the “System users” tab
Click the “Set SharePoint user” button
Office 365 screen will open to authenticate. Enter Office 365 credentials.
Once successfully log in, the integration user will appear. Only one integration is enough to set up the SharePoint connection.
Supported master templates
The following master templates have out of the box support for SharePoint integration:
Blank
Blank with e-sign
OfficeOutput
Settings for Blank Templates
SharePoint integration can be configured from the Settings section called “Integrations - SharePoint”.
Host is the custom domain that is used to log in your organizations' SharePoint. This value can be static, for example,
'documill.sharepoint.com'or dynamically come from a Salesforce field. Host field is required.Site is the site name within SharePoint that the document should be saved to. The value can be either static, such as
'Dynamo documents'or dynamic likevar.fieldName. Site value is also required.Folder is the folder name within that defined site above. You can save to a subfolder by giving the full folder path, for example: ‘Folder/Subfolder’ where “Folder” is the name of the first-level folder and “Subfolder” is the name of the 2nd level folder.
Save PDF to SharePoint saves the final PDF to SharePoint instead of the Salesforce record.
SharePoint link field is used to populate the SharePoint link to the generated document to a Salesforce field. Enter here the directory where the field should be saved to in format
objectAPIName.fieldAPIName. For example, object is Opportunity and the custom field is Document_SharePoint_Link__c, enter this boxOpportunity.Document_SharePoint_Link__c
Settings for Office Output and Leap Project Templates
Host is the custom domain that is used to log in your organizations' SharePoint. This value can be static, for example,
'documill.sharepoint.com'or dynamically come from a Salesforce field. Host field is required.Site is the site name within SharePoint that the document should be saved to. The value can be either static, such as
'Dynamo documents'or dynamic likevar.fieldName. Site value is also required.Folder is the folder name within that defined site above. You can save to a subfolder by giving the full folder path, for example: ‘Folder/Subfolder’ where “Folder” is the name of the first-level folder and “Subfolder” is the name of the 2nd level folder.
Save document to SharePoint saves the final document to SharePoint instead of the Salesforce record.
Overwrite determines if a saved file should overwrite its previous version or save as a new file.
Load template from SharePoint determines if the Office Content Template should be loaded from SharePoint instead of Salesforce.
SharePoint link field is used to populate the SharePoint link to the generated document to a Salesforce field. Enter here the directory where the field should be saved to in format
objectAPIName.fieldAPIName. For example, object is Opportunity and the custom field is Document_SharePoint_Link__c, enter this boxOpportunity.Document_SharePoint_Link__c
List of Commands
For templates that do not have the Integration tab to enable SharePoint integration, it is recommended to migrate to the new blank template where such Settings are enabled; or if one’s familiar with the Flow, it can also be customized by using the following set of commands within the Main Flow to manually enable the connection to SharePoint.