mscrm-addons.com logomscrm-addons.com logo
  • Release History
  • Knowledge Base
  • Documentation
  • Contact Support
  • Release History
  • Knowledge Base
  • Documentation
  • Contact Support
home/Knowledge Base/DocumentsCorePack(DCP)/Temporary Document Storage Locations in DocumentsCorePack

Temporary Document Storage Locations in DocumentsCorePack

877 views 1 Updated on November 22, 2024

Every document generated by DocumentsCorePack has to be temporarily stored in order to support its many processing options. By default, these files are stored within Dataverse itself.  Consequently, this will consume data capacity.  Over a long enough period, temporary documents can take up a considerable amount of space, leading customers to deploy bulk deletion jobs to deal with them.

By changing the temporary document storage location, this becomes unnecessary.  This article outlines the options available and how to change your temporary document storage location.  This not only optimizes your system’s performance but also helps avoid unnecessary data capacity costs.

Changing the storage location

To change the temporary document storage location, navigate to your service in the DocumentsCorePack Online Service Configuration.  The Temp Document Storage dropdown is located under the Configuration tab.

The Temp Document Storage dropdown under the Configuration tab
Figure 1: The Temp Document Storage dropdown under the Configuration tab

Under this dropdown, there are three options: Dataverse, Azure Blob by mscrm-addons.com, and Custom Azure Blob.

All three options of the Temp Document Storage dropdown
Figure 2: All three options of the Temp Document Storage dropdown

❶ Dataverse: All temporary documents will be stored in your Dataverse environment.  This option is selected by default.

❷ Azure Blob by mscrm-addons.com: Temporary documents are stored in Azure Blob storage managed by mscrm-addons.com.
Note: To ensure compliance with regional data handling preferences and avoid cross-continental data transfer, documents are stored in the EU, US, or Australia based on the customer’s location. All stored files are automatically deleted after seven days.

❸ Custom Azure Blob: Temporary documents will be stored on a custom Azure Blob storage of your choice.  If this option is selected, the user must provide the connection string to the storage account to be used in the Temp Document Storage Connection textbox that appears.

Figure 3: Access keys for Storage Accounts on Azure
The Temp Document Storage Connection textbox appearing under the Temp Document Storage dropdown
Figure 4: The Temp Document Storage Connection textbox appearing under the Temp Document Storage dropdown

In addition, make sure that CORS (Cross Origin Resource Sharing) is activated. You can activate CORS directly in Azure portal. It can be accessed under the Settings tab of your storage account.

 CORS Setting of storage accounts on Microsoft Azure
Figure 5: CORS Setting of storage accounts on Microsoft Azure

Enter a *.dynamics.com URL, *.crmX.dynamics.com URL, or the full URL of your Dynamics 365 environment as an allowed origin and save your changes. Once saved, any newly created temporary documents will be stored in the specified storage location.

Entering a URL under the Resource sharing
Figure 6: Entering a URL under the Resource sharing tab


That’s it! 
We appreciate your feedback! Please share your thoughts by sending an e-Mail to support@mscrm-addons.com.

Was this helpful?

1 Yes  1 No
Related Articles
  • Deploying DocumentsCorePack: Setup, Automation, and Real Business Impact in Dynamics365
  • Introducing the DocumentsCorePack Template Designer Office Add-In (Beta)
  • 3 Ways DocumentsCorePack Transforms Proposal, Quote, and Contract Creation
  • DeepSign for DocumentsCorePack 
  • Generate and send a document for e-signing using DeepSign
  • How to prepare a document for DeepSign
Latest Articles
  • What Happens After You Deploy AttachmentExtractor: Storage & Cost Savings in Dynamics 365
  • Deploying DocumentsCorePack: Setup, Automation, and Real Business Impact in Dynamics365
  • Introducing the DocumentsCorePack Template Designer Office Add-In (Beta)
  • How to Eliminate Excess Storage Costs in Microsoft Dynamics 365 Without Losing Access to Emails and Attachments
  • 3 Ways DocumentsCorePack Transforms Proposal, Quote, and Contract Creation
Popular Articles
  • DocumentsCorePack Template Designer – Getting Started
  • Step-by-Step: How to configure a One-Click-Action
  • Application Access for Dynamics 365
  • How to find your environment’s unique name in Microsoft Dynamics 365
  • How licenses are counted
Top Rated Articles
  • “Undefined”-labels in Chrome and Edge 114 and higher
  • Important information for Dynamics 365 online customers using DocumentsCorePack and/or AttachmentExtractor
  • How to activate the DocumentsCorePack Connector for PowerApps & Microsoft Flow
  • How to insert Condition Fields in DocumentsCorePack Templates designer
  • How licenses are counted
Categories
  • *News and General Infos* 64
  • Webinars 45
  • Template Designer(DCP 196
  • DocumentsCorePack(DCP 258
  • TelephoneIntegration (TI 65
  • AttachmentExtractor (AE 75
  • PowerSearch (PS 50
  • ActivityTools (AT 61
  • SmartBar (SB 54
  • GroupCalendar (GC 47
Our Vision

“We see it as our purpose to provide products that simplify and speed up our customers’ Microsoft Dynamics 365 experience.”

Knowledgebase
LogIn
mscrm-addons.com
  • Products
  • Online Shop
  • Downloads
  • My Account
About Us
  • About Us
  • Case Studies
  • Newsletter
  • Partner Program
  • Contact
Support
  • Support
  • Terms & Conditions
  • Documentation
  • Webinars
  • Legal Documents
  • Impressum
  • © 2025 www.mscrm-addons.com. All Rights Reserved.