Overview
You can now export Contract details from the Contract Lifecycle Management (CLM) system to your Enterprise Resource Planning (ERP) system by integrating them. You can automatically or manually generate .csv files containing a Contract's number, header information, periods of performance, CLINs/SLINs, modifications, and CLIN Mods. These files are pushed to SharePoint via the Dynamics API, where they can be picked up and used to update the ERP system.
This can also be configured to auto-generate the .csv file when a Contract reaches specific stages in the contract lifecycle or when certain events occur, such as the addition of a modification.
This guide takes you through the configuration steps required for SharePoint integration between your ERP and CLM system in Microsoft Dynamics.
Audience
Microsoft Dynamics Administrators
IT Support
Prerequisites
Ensure that TechnoMile Contracts Suite is already installed and configured. The version of this package must be 2024.2 or higher.
Integrating ERP and CLM Systems
Configuring SharePoint for Contract Export
Login to your Microsoft Dynamics instance.
Go to Advanced Settings by clicking the Settings icon.

Click the Advanced Find icon.

Select Product Configurations in the Look for field and click Results.

Click ContractExportSharePoint.

Specify your SharePoint site URL in the Value field and the folder/library name on your SharePoint site that is to be used for storing exported files in the JSON Value field and click Save & Close.

Configuring Automatic Export of Contract Data and Generation of Files Based on Events (Setting Up Custom Flows)
Go to Power Apps using App Launcher.

Select an Environment and click Solutions.


Click TechnoMile GRC Suite to open it.

Go to Cloud flows and click Create Contract Export Flow.

Click Edit.
The Create Contract Export Flow opens.
You can then call this flow from an action/event within the system. For example, you can initiate this process once the Contract Status field value changes from Draft to Negotiate by creating a separate power automate flow, tracking the Contract Status change action, and then triggering the Create Contract Export Flow from the newly created power automate flow.
