SharePoint - Configuration Guide

Change Summary

Release Date	Release Version	Change Description	Link
June 19th, 2026	2026.1.2	Enter SharePoint Documents tab label in SharePoint UI Control Config Product Configuration	Product Configurations
June 19th, 2026	2026.1.2	Configure SharePoint on Agreement entity	SharePoint Entity-based Configurations for Agreement
April 13th, 2026	2026.1	Describes standard specifications for SharePoint integration with Contracts Suite entities	SharePoint Integration with Contracts Suite Entities
April 13th, 2026	2026.1	Describes standard specifications for SharePoint integration with Contracts Suite’s Pre-award entities	SharePoint Integration with Contracts Suite’s Pre-award Entities
April 13th, 2026	2026.1	Describes standard specifications for SharePoint integration with other Contracts Suite entities	SharePoint Integration with Other Contracts Suite Entities

Overview

SharePoint Connector integrates TechnoMile’s Contracts Suite with your online Microsoft SharePoint site. This allows your team to centralize all documents and files associated with a Contract into a single, online repository and then quickly and conveniently access them directly from your Contracts solution.

TechnoMile’s SharePoint Connector auto-generates a standardized folder structure upon the creation of a new Contract Record, enforcing clean, consistent organization of files in SharePoint and making them easy for users to find and share.

Audience

Microsoft Dynamics Administrators
IT Support

Prerequisites

Ensure that TechnoMile’s Contracts Suite is already installed and configured. The version of this package must be 2026.1 or higher.

Power Automate Configurations

Login to your Microsoft Dynamics instance.
Click the gear icon and select Advanced Settings.
Click the search icon.
Click the Search for rows in a table using advanced filters link.
Search for and select Power Automate Configs using table search and click Continue.
Scroll down and open the Metadata Generation For SharePoint Folder Structure Power Automate Configuration
Specify the Flow URL and click Save.
NOTE:
You must retrieve the Flow URL field value from your Cloud Flow of the same name in Power Automate.
Similarly, open the Generic - Create SharePoint Folder Structure Power Automate Configuration to specify its Flow URL.
Similarly, open the Generic - SharePoint Connector Power Automate Configuration to specify its Flow URL.
Similarly, open the Generic - SharePoint Metadata Update Power Automate Configuration to specify its Flow URL.
Similarly, open the Generic - Rename Entity SharePoint Folder Name Power Automate Configuration to specify its Flow URL.
Similarly, open the Generic - Child Metadata Update Power Automate Configuration to specify its Flow URL.

SharePoint Entity-based Configurations

For Contract

Go back to search for and select Share Point Configurations using table search and click Continue.
Scroll down and open the Contract entity.
Enter details in mandatory fields such as Entity Name, Name of Root Folder, Schema Name, Entity Set Name, Relative URL SharePoint, and SharePoint Base URL, in other fields such as Folder Structure and Metadata JSON, and click Save.
To retrieve an Entity Set Name perform the following steps:
1. Go to the following URL - https://{your dynamics CRM url}/API/data/v9.2/EntityDefinitions(LogicalName='{entity logical name}')
2. Search for and retrieve the Entity Set Name.
  You can also enter any or all of the below listed combinations for creating separate entity-based SharePoint Configurations:
- Record Type as blank and Is Child Object set to No
- Record Type selected and Is Child Object set to No
- Record Type as blank and Is Child Object set to Yes
- Record Type selected and Is Child Object set to Yes
  NOTES:
  - If you specify a Record Type, then you must also specify a Record Type Logical Name.
  - If you set Is Child Object to Yes, then you must also to specify a Schema Name of Parent.

For Agreement

In the list of SharePoint Configurations, scroll down and open the Agreement entity.
Enter details in mandatory fields such as Entity Name, Name of Root Folder, Schema Name, Entity Set Name, Relative URL SharePoint, and SharePoint Base URL, in other fields such as Folder Structure, and click Save.
To retrieve the Entity Set Name, refer to SharePoint Contract Configurations.

Product Configurations

Go back to search for and select Product Configurations using table search and click Continue.
Open the SharePoint Special Characters Product Configuration.
Specify the Value and click Save.
NOTE:
The Value field must contain a list of special characters that are to be allowed during creation of a SharePoint document location, without any separators.
Similarly, open the Child Record Metadata Update Product Configuration.
Set Value as false and click Save.
NOTE:
This is an on-demand functionality so only if it is required, then its Value must be set to true. Else by default, its Value is set to false.
Similarly, open the Child Record Metadata Entities Product Configuration.
Specify the JSON Value and click Save.
NOTE:
The JSON Value field must contain details of Entity Logical Names (.i.e. Logical Names of Child Entities for which Child Metadata update functionality is required), Entity Set Names, and their related Contract Lookup Fields.
In Advanced Settings, go to Solutions and open Default Solution.
Go to Objects, scroll down, and expand Tables.
Scroll down under Tables, expand Contract, click Forms, and open the Main Form type such as Contract - Contracts.
Go to the SharePoint-related tab on the form and copy the value in the Name field.
Alternatively, if the tab is available under Related – Common, click the three dots icon, scroll down the subsequent menu, click Documents, and copy the value in its Label field.
Go back to search for and select Product Configurations using table search and click Continue.
Open the SharePoint UI Control Config Product Configuration.
Paste the Label field value into the JSON Value as shown below for Contracts and click Save.
Similarly, you can copy and paste the SharePoint Documents tab label for all other entities into the JSON Value of the SharePoint UI Control Config Product Configuration, as per your requirements.
Go to Contracts and create a Contract record.
The following SharePoint folder structure is being created… message displays.
Once Contract is created which may take some time, the following SharePoint folder structure has been created… message displays.
Click the three dots icon on the ribbon and note that the Generate Documents button is now visible.
Click the three dots icon on the tabs and note that the Documents tab is now visible under Related - Common.

Documents tab opens with SharePoint folder structure on it.

Power Automate Flows Customizations

Go to Power Automate using App Launcher.
Select your Environment and click My flows.
Go to Cloud flows and note the below highlighted sample flows that come out-of-the box.
Open the SPS - Contract flow.
Click Edit.
SPS - Contract flow opens.
Expand the first action that is highlighted below to enter the following information:
1. Table name as name of the entity for which SharePoint folders are to be created.
2. Select columns as logical names of all the fields in the form of a comma-separated list, which you had entered in the SharePoint Configuration record of the same entity in its Metadata JSON field.
  NOTE:
  If in case the Metadata JSON field of a SharePoint Configuration record of an entity is set to blank, then the Select columns must be set to the value entered in its Name of Root Folder field.
Expand Entity Logical Name to enter Value as logical name of the entity.
Scroll down and expand Set variable Record ID to enter Value as Unique Identifier of the entity record.
Scroll down and expand Switch.
Expand Case and then expand Check SDK Message.
Scroll down and expand Run a Child Flow to select Child Flow as Generic - Remove SharePoint Special Characters and enter Record Name as Folder Name.
Expand Set Variable Folder Name Value to set the output of this flow back to the variable Folder Name.
Scroll down and expand Create Document Location with Regarding and then expand Show advanced options.
Scroll down and enter Regarding (Contracts) as Entity Set Record ID.
Scroll up and click Save.
Similarly, you can edit any of the sample SPS - Rename Entity flows by:
1. Setting Select columns to the value entered in the Name of Root Folder field of the related SharePoint Configuration record for that entity
2. Setting Record ID Value to Unique Identifier of that entity record

Important:
Note that once all the above configurations are completed, an out-of-the-box SharePoint Documents tab will display on all your configured entities such as Contract record page. However, in rare cases where you do not have SharePoint configured in your organization but entities still have a relationship with TM Documents and the related entity forms are configured for it, then the Documents tab of TM Documents will display instead.

SharePoint Integration with Contracts Suite Entities

Agreement

The out-of-the-box Contracts Suite’s Agreement Management add-on that includes the Agreement entity is integrated with SharePoint with the following standard specifications:

Table (Dataverse)	Agreement Id (clm_agreementid)
Standard Scope	Connection of Contracts Suite data table to one (1) Document Library/Set within one (1) SharePoint Site Auto-generation of one (1) folder per record Auto-generation of sub-folder structure One-way metadata push from CLM to SharePoint

Component Type	Standard Configuration	Notes
Integration Flow	Create Document Location	Document is generated under the Root Folder after clicking the Generate Document button on ribbon.
Document Library	Agreement
Nested Location	Not nested, top-level folder
Folder Name	[Agreement ID]
Sub-folders	None
Metadata	None

Contract

The out-of-the-box Contracts Suite’s Contract entity is integrated with SharePoint with the following standard specifications:

Table (Dataverse)

Contract (new_contractvehicles)

Standard Scope

Connection of Contracts Suite data table to one (1) Document Library/Set within one (1) SharePoint Site

Auto-generation of one (1) folder per record
Auto-generation of sub-folder structure
One-way metadata push from CLM to SharePoint

Component Type	Standard Configuration	Notes
Integration Flows	SPS - Contract Generic - Remove SharePoint Special Characters Generic - SharePoint Connector Generic - Get SharePoint Configuration Generic - Create SharePoint Folder Structure	Includes Folders 01-15 Folder 00 is not included Agreements use an independent process for SharePoint folder creation. As a result, the product does not create Agreement folders within the corresponding Contract SharePoint folder. The JSON configuration has also been updated to reflect this behavior.
Document Library	Contract
Nested Location	Not nested, top-level folder
Folder Name	Contract Name (new_name)	Takes the value of attribute mentioned in the Name of Root Folder column in SharePoint Configurations record
Sub-folders	01 Contract Details 02 Contract Briefs 03 Contract Mods 04 CPARS 05 Deliverables 06 CDRLs 07 OCIs 08 Wage Determinations 09 Labor Cats and Rates 10 LOFs 11 Closeouts 12 Subcontracts 13 Task Orders 14 Adverse Actions 15 At-Risk Fundings	01 - During the conversion of a Proposal to a Contract, the associated documents are copied from the Proposal to the corresponding folder in the Contract. 02 - Contains Contract Brief documents 04 - Contains Self Evaluation documents inside the child folder of CPARS root folder 10 - Contains LOF Documents 14 & 15 - Folder gets created at run time when the user creates an Adverse Action record and At-Risk Funding record
Metadata	ContractNumber (new_tm_toma__contract_number__c) Proposal (clm_proposal) CompetitionType (clm_competitiontype) ContractDollarGoal (clm_plannedgoaldollar) EffectiveDate (new_tm_clm__effective_date_of_action__c)

Task Order

The out-of-the-box Contracts Suite’s Task Order entity is integrated with SharePoint with the following standard specifications:

Table (Dataverse)	Task Order (new_contractvehicles)
Standard Scope	Connection of Contracts Suite data table to one (1) Document Library/Set within one (1) SharePoint Site Auto-generation of one (1) folder per record Auto-generation of sub-folder structure One-way metadata push from CLM to SharePoint

Component Type	Standard Configuration	Notes
Integration Flows	SPS - Contract Generic - Remove SharePoint Special Characters Generic - SharePoint Connector Generic - Get SharePoint Configuration Generic - Create SharePoint Folder Structure	This is when the Contract Type = Task Order
Document Library	Contract (Nested)	Nested under parent Contract in folder 13 - Task Orders
Nested Location	Contract
Folder Name	Contract Name (new_name)	Takes the value of attribute mentioned in the Name of Root Folder column in SharePoint Configurations record
Sub-folders	01 Contract Details 02 Contract Briefs 03 Contract Mods 04 CPARS 05 Deliverables 06 CDRLs 07 Contracts 08 Subcontracts 09 OCIs 10 LOFs
Metadata	ContractNumber (new_tm_toma__contract_number__c) Proposal (clm_proposal)

Contract Mod

The out-of-the-box Contracts Suite’s Contract Mod entity is integrated with SharePoint with the following standard specifications:

Table (Dataverse)	Contract Mod (clm_contractmod)
Standard Scope	Connection of Contracts Suite data table to one (1) Document Library/Set within one (1) SharePoint Site Auto-generation of one (1) folder per record Auto-generation of sub-folder structure One-way metadata push from CLM to SharePoint

Component Type	Standard Configuration	Notes
Integration Flows	SPS - Contract Mod Generic - Remove SharePoint Special Characters Generic - SharePoint Connector Generic - Get SharePoint Configuration Generic - Create SharePoint Folder Structure
Document Library	Contract (Nested)
Nested Location	Contract
Folder Name	Name (clm_modname)	Takes the value of attribute mentioned in the Name of Root Folder column in SharePoint Configurations record
Sub-folders	00 Funding Obligations 01 Contract Details 02 Contract Briefs
Metadata	AwardType (clm_awardtype) Subcontract (clm_subcontract)

CPARS

The out-of-the-box Contracts Suite’s CPARS entity is integrated with SharePoint with the following standard specifications:

Table (Dataverse)	CPAR (clm_cpar)
Standard Scope	Connection of Contracts Suite data table to one (1) Document Library/Set within one (1) SharePoint Site Auto-generation of one (1) folder per record Auto-generation of sub-folder structure One-way metadata push from CLM to SharePoint

Component Type	Standard Configuration	Notes
Integration Flows	SPS - CPAR Generic - Remove SharePoint Special Characters Generic - SharePoint Connector Generic - Get SharePoint Configuration Generic - Create SharePoint Folder Structure
Document Library	Contract (Nested)
Nested Location	Contract
Folder Name	Name (clm_name)	Takes the value of attribute mentioned in the Name of Root Folder column in SharePoint Configurations record
Sub-folders	[ROOTFOLDER]
Metadata	ContractingOffice (clm_contractingoffice) CompetitionType (clm_competitiontype

Organizational Conflict of Interest (OCI)

The out-of-the-box Contracts Suite’s OCI entity is integrated with SharePoint with the following standard specifications:

Table (Dataverse)	OCI (clm_oci)
Standard Scope	Connection of Contracts Suite data table to one (1) Document Library/Set within one (1) SharePoint Site Auto-generation of one (1) folder per record Auto-generation of sub-folder structure One-way metadata push from CLM to SharePoint

Component Type	Standard Configuration	Notes
Integration Flows	SPS - OCI Generic - Remove SharePoint Special Characters Generic - SharePoint Connector Generic - Get SharePoint Configuration Generic - Create SharePoint Folder Structure
Document Library	Contract (Nested)
Nested Location	Contract
Folder Name	OCI Name (clm_name)	Takes the value of attribute mentioned in the Name of Root Folder column in SharePoint Configurations record
Sub-folders	[ROOTFOLDER]
Metadata	OCIManager (clm_ocimanager) MDAP (clm_majordefenseaquisitionprogrammdap

Adverse Action

The out-of-the-box Contracts Suite’s Adverse Action entity is integrated with SharePoint with the following standard specifications:

Table (Dataverse)	Adverse Action (clm_adverseaction)
Standard Scope	Connection of Contracts Suite data table to one (1) Document Library/Set within one (1) SharePoint Site Auto-generation of one (1) folder per record Auto-generation of sub-folder structure One-way metadata push from CLM to SharePoint

Component Type	Standard Configuration
Integration Flows	Adverse Action - Create SharePoint Folder Structure Generic - Remove SharePoint Special Characters
Document Library	Contract (Nested)
Nested Location	Contract
Folder Name	Name (clm_name) + Date Received (clm_datereceived)
Sub-folders	[ROOTFOLDER]
Metadata	NA

At-Risk Funding

The out-of-the-box Contracts Suite’s At-Risk Funding entity is integrated with SharePoint with the following standard specifications:

Table (Dataverse)	At-Risk Funding (clm_atriskfunding)
Standard Scope	Connection of Contracts Suite data table to one (1) Document Library/Set within one (1) SharePoint Site Auto-generation of one (1) folder per record Auto-generation of sub-folder structure One-way metadata push from CLM to SharePoint

Component Type	Standard Configuration
Integration Flows	Risk Funding - Create SharePoint Folder Structure Generic - Remove SharePoint Special Characters
Document Library	Contract (Nested)
Nested Location	Contract
Folder Name	At-Risk Request ID (clm_atriskrequest)
Sub-folders	[ROOTFOLDER]
Metadata	NA

Subcontract

The out-of-the-box Contracts Suite’s Subcontract entity is integrated with SharePoint with the following standard specifications:

Table (Dataverse)	Subcontract (fedcap_subcontract)
Standard Scope	Connection of Contracts Suite data table to one (1) Document Library/Set within one (1) SharePoint Site Auto-generation of one (1) folder per record Auto-generation of sub-folder structure One-way metadata push from CLM to SharePoint

Component Type	Standard Configuration	Notes
Integration Flows	SPS - Subcontract Generic - Remove SharePoint Special Characters Generic - SharePoint Connector Generic - Get SharePoint Configuration Generic - Create SharePoint Folder Structure
Document Library	Contract (Nested)
Nested Location	Contract
Folder Name	Subcontract Name (fedcap_name)	Takes the value of attribute mentioned in the Name of Root Folder column in SharePoint Configurations record
Sub-folders	01 Subcontract Details 02 Mods 03 Labor Cats and Rates 04 Closeout
Metadata	SubcontractValue (clm_subcontractvalue), CurrentFunding (fedcap_currentfunding), SubcontractAdministrator (clm_subcontractadministrator)

SharePoint Integration with Contracts Suite’s Pre-award Entities

Solicitations

The out-of-the-box Contracts Suite’s Pre-award add-on that includes the Solicitations entity is integrated with SharePoint with the following standard specifications:

Table (Dataverse)	Solicitation (clm_solicitation)
Standard Scope	Connection of Contracts Suite data table to one (1) Document Library/Set within one (1) SharePoint Site Auto-generation of one (1) folder per record Auto-generation of sub-folder structure One-way metadata push from CLM to SharePoint

Component Type	Standard Configuration
Integration Flows	Solicitation - Create SharePoint Folder Generic - Remove SharePoint Special Characters
Document Library	Solicitation
Nested Location	Not nested, top-level folder
Folder Name	Solicitation Number (clm_solicitationnumber)
Sub-folders	[ROOTFOLDER]
Metadata	NA

Proposals

The out-of-the-box Contracts Suite’s Pre-award add-on that includes the Proposals entity is integrated with SharePoint with the following standard specifications:

Table (Dataverse)	Proposal (clm_proposal)
Standard Scope	Connection of Contracts Suite data table to one (1) Document Library/Set within one (1) SharePoint Site Auto-generation of one (1) folder per record Auto-generation of sub-folder structure One-way metadata push from CLM to SharePoint

Component Type	Standard Configuration
Integration Flows	Proposal - Create SharePoint Folder Generic - Remove SharePoint Special Characters
Document Library	Proposal
Nested Location	Not nested, top-level folder
Folder Name	Proposal Title (clm_name)
Sub-folders	Negotiation
Metadata	NA

Negotiations

The out-of-the-box Contracts Suite’s Pre-award add-on that includes the Negotiations entity is integrated with SharePoint with the following standard specifications:

Table (Dataverse)	Negotiation (clm_negotiation)
Standard Scope	Connection of Contracts Suite data table to one (1) Document Library/Set within one (1) SharePoint Site Auto-generation of one (1) folder per record Auto-generation of sub-folder structure One-way metadata push from CLM to SharePoint

Component Type	Standard Configuration	Notes
Integration Flows	Negotiations - Create SharePoint Folder Generic - Remove SharePoint Special Characters
Document Library	Proposal (Nested)	A Negotiation record is created within its parent Proposal record in CRM. As a result, the SharePoint folder for the Negotiation record is created under the Negotiation folder within the parent Proposal record’s SharePoint folder in the Proposal document library. Similarly, the document location for the Negotiation record is created under the Negotiation document location, which exists within the parent Proposal document location. The folder structure in SharePoint is as follows: Proposal (Document Library) -> Proposal Record (SharePoint Folder) -> Negotiation (SharePoint Folder) -> Negotiation Record (SharePoint Folder) For example, if we create a Negotiation record with name N2026-0083 under a parent Proposal record with name TEST PROPOSAL 1303, then its SharePoint folder will be created such as: Proposal -> TEST PROPOSAL 1303 -> Negotiation -> N2026-0083
Nested Location	Negotiation
Folder Name	Negotiation Record No. (clm_negotiationrecordno)
Sub-folders	[ROOTFOLDER]
Metadata	NA

TINA Certifications

The out-of-the-box Contracts Suite’s Pre-award add-on that includes the TINA Certifications entity is integrated with SharePoint with the following standard specifications:

Table (Dataverse)	TINA Certification (clm_tinacertification)
Standard Scope	Connection of Contracts Suite data table to one (1) Document Library/Set within one (1) SharePoint Site Auto-generation of one (1) folder per record Auto-generation of sub-folder structure One-way metadata push from CLM to SharePoint

Component Type	Standard Configuration	Notes
Integration Flows	TINA Certification - Create SharePoint Folder Generic - Remove SharePoint Special Characters
Document Library	TINA Certification
Nested Location	Not nested, top-level folder
Folder Name	TINA ID (clm_name)
Sub-folders	[ROOTFOLDER]	TINA Certification document will be generated under the TINA Certification Root Folder
Metadata	NA

SharePoint Integration with Other Contracts Suite Entities

The out-of-the-box Contracts Suite contains other entities that are also integrated with SharePoint with the following standard specifications:

Entities	Parent Entity	Naming Convention (Display/Logical Name)	Sub-folders (Nested under Parent Entity)	Metadata	Flow already present in OOTB?
Deliverables	Contract	N/A	N/A	N/A	No
CDRLs	Contract	N/A	N/A	N/A	No
Wage Determinations	Contract	N/A	N/A	N/A	No
Labor Cats and Rates	Contract	N/A	N/A	N/A	No
Other Entities
BOEs	N/A	N/A	N/A	N/A	No
Cost Memos	N/A	N/A	N/A	N/A	No
Delegation Requests	N/A	N/A	N/A	N/A	No
External POCs	N/A	N/A	N/A	N/A	No
WBS	N/A	N/A	N/A	N/A	No
Accounts	N/A	N/A	N/A	N/A	No

Documentation Index