Subfolder Structure
With the subfolder structure feature, existing folders and files in SharePoint can be conveniently duplicated or replicated by simply configuring the path of the main folder in the Entity configuration.
This feature is highly versatile and can be used in various scenarios:
Policy and Document Management: Create a folder with subfolders containing different documents such as policies, product assets, terms and conditions, and more. This ensures organized and efficient document management.
Onboarding New Customers or Team Members: An executive can easily duplicate a structured folder in SharePoint for newly onboarded customers or new team members. This can include a sheet of Points of Contact (POCs), training materials, and other essential documents.
The possibilities are endless, providing a streamlined approach to managing and replicating folder structures and their contents within SharePoint.
Configuration:
To replicate folders and files in SharePoint using the subfolder structure feature, follow these steps:
Navigate to SharePoint Security Sync’s Entity Configuration:
Go to Entity Configuration and select Account.

• Open the Create Custom Folder Structure tab. Here, you will find the Subfolder Template Path field.

Set the Subfolder Template Path:
Copy the title of the main folder you want to replicate by default.

Paste the folder title inside the Subfolder Template Path field.

Click Save to save the configuration.

Example Using Attach2Dynamics UI:
When the user clicks on Attach2Dynamics, a document location is created in the background.

The configuration then creates a copy of the files and folders inside the configured folder

As shown in the screenshot, folders, and files are replicated by default.

This link redirects to the replicated SharePoint Folder.

This process ensures that the folder structure, along with its contents, is conveniently duplicated in SharePoint.
Sub-Folder Template Path Support (FetchXML-Based)
This feature enables automatic creation of a folder structure in SharePoint based on conditions defined using FetchXML. Whenever a Dynamics 365 record meets one of the configured conditions, the system replicates a pre-defined SharePoint template folder structure under that record’s SharePoint location. A default template can also be configured to handle cases where no condition matches.
This feature is highly versatile and can be used in various scenarios:
Helps create different folder templates based on business requirements such as region, department, customer type, or any CRM field.
Ensures the right template is automatically applied to each record.
Allows organizations to maintain standardized folder structures across records while still supporting variations needed for different business scenarios.
Configuration:
1. Go to Entity Configuration and select Account

2. Open the Create Custom Folder Structure tab. In the Subfolder Template Path section, click on New Sub Folder Template Path.

3. In the FetchXML field, enter the condition that determines when the folder template should be applied.

4. Copy and paste the SharePoint Template Path. This represents the folder structure that will be replicated when the FetchXML condition is met.


5. Click Save and Close.

6. This step is optional. Configure a Default Template Path to be used when none of the FetchXML conditions match.


7. Click on Save to save the configuration.

Example using Attach2Dynamics UI:
1. A user creates a new record in the CRM when the address entered is USA.

2. When the record is saved and the user clicks on Attach2Dynamics, the configured FetchXML condition is evaluated in the background.

3. If the condition matches, the system automatically creates a copy of the configured SharePoint folder and file structure under the record’s SharePoint location.

4. This link redirects to the replicated SharePoint Folder.


5. If a default template path is configured, and the user creates a record where the Address field contains “English” or is left empty, the default folder structure is automatically applied instead.


Last updated
Was this helpful?