Setting up connectors

Creating a Microsoft Project connector

Modified on Tue, 17 Nov at 12:02 AM

TABLE OF CONTENTS

  1. Introduction
  2. At a glance
  3. What to ask your IT administrator for
  4. Open the connector wizard
  5. Step 1: General
  6. Step 2: Components
  7. Step 3: Storage and sign-in: Web Storage · SharePoint · Local File
  8. Step 4: Settings
  9. Step 5: Complete, test and persist
  10. How files are added, and file rules: Web Storage · SharePoint and Local File
  11. Messages and what to do
  12. Questions and answers
  13. Related articles

Introduction

This article shows you, step by step, how to create a Microsoft Project connector. This connector lets SchedEx read schedules from Microsoft Project files (.mpp) and send them to a partner through an Exchange Agreement.

A Microsoft Project connector only sends. SchedEx reads your .mpp files, but it cannot write one. To receive a partner's schedule, use another connector on your side, for example Excel.

Who can do this: a user with the Tenant Setup role in SchedEx.

You do not need to be technical. You only need to decide where the files are kept. If they are kept in SharePoint, section 2 lists what to ask your IT department for.

Not sure where to keep the files? Read Choosing where your schedule files are stored. It compares the three storage types in full. Using Excel or Primavera P6 files instead? See Creating a Microsoft Excel connector or Creating a Primavera P6 XER file connector.


1. At a glance

Creating the connector takes about five minutes.

  1. Decide where the .mpp files will be kept (section 6).
  2. Ask your IT department for the SharePoint values, if you choose SharePoint (section 2).
  3. Fill in the five-step wizard in SchedEx (sections 3 to 7).
  4. Test the connector, and create its schedules (section 8).

Which storage type? Pick one, then jump straight to its parts of this article. The other storage types' sections can be skipped.

Storage type In plain words Set it up in the wizard How files are added After saving
Web Storage (files) People upload the files on the SchedEx Files page. No IT setup. The default, and the right choice for most organizations. Option A Web Storage (files) Create the schedules
SharePoint SchedEx reads the files from a SharePoint folder. Needs IT setup. Option B. IT setup: Connecting SchedEx to SharePoint SharePoint and Local File Test and persist
Local File SchedEx reads the files from a folder on the PC or server that runs the transfer. Option C SharePoint and Local File Test and persist

The full comparison is in Choosing where your schedule files are stored.

Checklist before you open the wizard:

  • I know which storage type to use.
  • I know whether transfers run on a person's PC (Desktop Client), on a server (Autonomous Component), or both.
  • SharePoint only: I have the folder's SharePoint address, the Client ID and the Tenant ID from IT.
  • Local File only: I have the folder path, and the folder already contains at least one .mpp file.

2. What to ask your IT administrator for

With Web Storage (files) you need nothing from IT. Skip to section 3.

With SharePoint or Local File, ask your IT department or SharePoint administrator for the items below. Tell them whether SchedEx will read the files from users' PCs (Desktop Client), from a server (Autonomous Component), or both.

Ask for Why SchedEx needs it Where it goes
Only if SharePoint: the address of the SharePoint folder that holds the .mpp files. So SchedEx knows where to read the files. Step 3: SharePoint URL
Only if SharePoint: the Application (client) ID of the Microsoft Entra ID app registered for SchedEx. SchedEx signs in to SharePoint through this app. Step 3: Microsoft Entra ID Client ID (For SharePoint)
Only if SharePoint: your organization's Tenant ID in Microsoft Entra ID. Tells Microsoft which organization to sign in to. Step 3: Microsoft Entra Tenant Id (For SharePoint)
Only if SharePoint: access for the app to the SharePoint site (read access is enough, because this connector only reads). Share Configure-SharePoint-Access with them. Without it, SchedEx cannot see the folder. Set up in Microsoft Entra ID and SharePoint by IT
Only if SharePoint and the Autonomous Component: the app's certificate installed on the Autonomous Component's server. The Autonomous Component signs in with the certificate, without a person. Set up on the server by IT
Only if SharePoint and the Desktop Client: access to the SharePoint folder for each person who runs transfers. In the Desktop Client, SchedEx reads SharePoint as the signed-in person. Set up in SharePoint by IT
Only if Local File: the folder path, and read access to it for users' PCs or for the Autonomous Component's server. SchedEx reads the folder from the computer that runs the transfer. Step 3: File System Root Folder Path

No password is stored: with SharePoint, SchedEx signs in with a Microsoft account, and with Web Storage or Local File no sign-in is needed, so this connector stores no password or secret. Read how SchedEx protects the credentials of other connectors in Checking your connectors.


3. Open the connector wizard

  1. Select Setup in the top menu.
  2. On the Connector List card, select New Connector.

The Setup page with the New Connector button on the Connector List card The Setup page. New Connector is on the Connector List card.

The New Connector wizard opens on the right. It has five steps: General, Components, Authentication, Settings and Complete. Every field has an ⓘ icon. Point at it to see a short help text. Next stays grey until every required field on the step is filled in.


4. Step 1: General

Field What to enter
Connector Name (required) A name that tells your colleagues which files this is, for example MS Project - Web storage or MS Project - Projects SharePoint. The name is shown everywhere the connector is used, such as in Configs and Exchange Agreements.
Host System (required) Select Microsoft Project.
Import from existing (optional) Copies the settings of a connector you already have, so that you only change what is different.

Step 1 of the wizard with the Microsoft Project card selected Step 1: the Microsoft Project card selected.

Select Next.


5. Step 2: Components

An execution component is the SchedEx program that runs the transfer and reads the files.

Option What it means Choose it when
Desktop Client The SchedEx desktop program on a user's PC. Someone must be signed in to start a transfer. People start transfers by hand.
Autonomous Component A SchedEx service that runs on a server, without a person. Transfers must run automatically on a schedule.

You can select both. The connector then gets one sign-in profile for each component. With SharePoint, you fill in both in the next step. The storage type, the SharePoint address and the folder path are the same for both.

Step 2 with both components selected Step 2 with both components selected.

Select Next.


6. Step 3: Storage and sign-in

The step is called Authentication. At the top, under Authentication profiles, you see one tab for each component you selected in Step 2. Then choose the Storage Type. The fields below it change to match your choice.

Storage Type You enter Desktop Client Autonomous Component
Web Storage (files) Nothing Yes Yes
SharePoint Authentication Method, SharePoint URL, Client ID and Tenant ID Yes, with Microsoft sign-in Yes, with a certificate
Local File File System Root Folder Path Yes Yes

Option A: Web Storage (files)

Select Web Storage (files). This is selected by default. There is nothing else to fill in, and the Authentication Method list is hidden.

Step 3 with Web Storage (files) selected Web Storage (files): no further fields.

Only one web storage connector of each type. Your organization can have one Microsoft Project web storage connector for the Desktop Client and one for the Autonomous Component. If one already exists, SchedEx refuses to save a second one (see section 10). Use the existing connector instead.

Done with this storage type? Skip the other options and go to Step 4: Settings.

Option B: SharePoint

Before you start: your IT department must have set up SharePoint access for SchedEx. What they need to do, which addresses work and how SchedEx signs in are explained in Connecting SchedEx to SharePoint. This section only covers the fields in this wizard.

Select SharePoint. Then fill in the fields below. If you selected both components, fill in the Authentication Method, Client ID and Tenant ID on each tab.

Step 3 with SharePoint selected on the Desktop Client tab SharePoint on the Desktop Client tab: Microsoft Entra ID (Interactive).

Field What it means Example
Authentication Method (required) How SchedEx signs in to SharePoint. The list only offers the method that works for the tab you are on. See below.
SharePoint URL (required) The address of the SharePoint folder that holds the .mpp files. A site address uses that site's default document library. To use another library or folder, open it in SharePoint and copy the address from the browser address bar. The folder must already exist. https://contoso.sharepoint.com/sites/projects/Schedules/2026
Microsoft Entra ID Client ID (For SharePoint) (required) The Application (client) ID of the app that SchedEx uses for SharePoint. Found in the Azure portal under App registrations → your app. xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Microsoft Entra Tenant Id (For SharePoint) (required) Your organization's Tenant ID. Found in the Azure portal under Microsoft Entra ID → Overview. xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Authentication methods:

Method Tab What happens
Microsoft Entra ID (Interactive) Desktop Client The first time the connector runs, a browser window opens. The user signs in with their Microsoft work account. SchedEx then reads SharePoint as that user.
Microsoft Entra ID App Certificate (SharePoint) Autonomous Component The Autonomous Component signs in on its own, with the certificate that IT installed on its server. No person is needed.

Step 3 with SharePoint selected on the Autonomous Component tab SharePoint on the Autonomous Component tab: App Certificate.

When you save, SchedEx checks the SharePoint address. If it ends in what looks like a file name, for example .../Schedules/Plan.mpp, it asks Is that a file or a folder?. SchedEx always reads files from a folder. Select Use this folder to save the folder's address, or Keep what I entered if the name really is a folder.

Done with this storage type? Skip the other options and go to Step 4: Settings.

Option C: Local File

Select Local File. Then fill in one field.

Step 3 with Local File selected Local File: the folder path.

Field What it means Example
File System Root Folder Path (required) The folder that holds the .mpp files. Use a full path. The folder is read on the PC or server that runs the transfer, so the path must work there. For a SharePoint folder that OneDrive keeps in sync on each PC, you can use %USERPROFILE%. \\fileserver\Schedules\MSP or %USERPROFILE%\Contoso\Projects - Documents

Select Next when all required fields are filled in.


7. Step 4: Settings

What you see depends on the storage type.

With SharePoint or Local File, there is one optional setting:

Settings step for a Microsoft Project connector Step 4 with SharePoint or Local File: All files have same user fields.

Setting What it means Default
All files have same user fields Switch this on if every .mpp file in the folder uses the same custom fields (the same user field names). SchedEx then reads the custom fields once, from the first file in alphabetical order, and all schedules share them. Schedules that share the same fields can be used together in one Config. Switch it off if the files have different custom fields. Each file then gets its own set. On

With Web Storage (files), the step only says No additional settings are required for this connector type. Click 'Create Connector' to save. With web storage you choose, for each file you upload, whether it shares its fields with another schedule (see section 9). That is why the setting is hidden.

Select Create Connector to save.


8. Step 5: Complete, test and persist

The last step confirms that the connector is saved. Select View Connector to open it, or Close.

What happens next depends on the storage type.

Web Storage (files): create the schedules

A web storage connector does not search for files, so there is no Persist. Instead, create one schedule for each project you will send:

  1. Open the connector, open its menu and select New MPP File. (You can also do this on Files

    Schedules & Templates.)

  2. Choose a sample .mpp file. Name it exactly as you want the schedule to be named, for example North-Platform-2026.mpp. SchedEx only reads the file's fields, not its rows. A file with the right custom fields, even an empty one, is enough.
  3. Optional: tick Reuse an existing schedule's host fields to share fields with a schedule you already have, so that one Config covers both.
  4. When it finishes you see Uploaded. Schedule "…" was created with … host fields.

You can also run Test in the Desktop Client. For web storage it only confirms the setting, and shows Web storage configured.

The Next Steps list on the Complete step may still mention Persist. For a web storage connector, use New MPP File instead.

SharePoint or Local File: test and persist

Both run from the SchedEx desktop client, on a PC that can reach the folder:

  1. Test the connector. In the desktop client, open Connectors and select Test on the connector's row. SchedEx opens the folder and reads the first .mpp file.
    • Connected means the folder, the sign-in and the file all work.
    • Test Failed: followed by a message means something is wrong. See section 10.
    • With SharePoint, a Microsoft sign-in window may open during the test.
    • The folder must contain at least one .mpp file, or the test fails.
  2. Persist the connector. Select Persist on the same row. SchedEx reads every .mpp file in the folder and creates one schedule for each, named after the file. It also reads the files' fields, so that you can map them in Configs. When it finishes you see Host System data stored successfully!

Persist again whenever you add a new .mpp file to the folder, or change its custom fields.

If transfers run on the Autonomous Component

A test in the desktop client runs from your PC. It proves that your PC can reach the folder, not that the Autonomous Component's server can. To check the server:

  • Persist from the server (SharePoint and Local File only). In the SchedEx web app, open Setup > Connectors, open the connector and select Persist Within 3 Minutes. The Autonomous Component picks up the request and reads the folder itself.
  • Ask a Tenant Admin to check the dashboard. In Clients > Autonomous Component > Dashboard, the Connectors panel shows each connector's health and its latest persist. The connector should be Healthy. If it is Unhealthy, point at the error icon to see why. See Reading the Autonomous Component Dashboard.

Check the connector later

In the web app, Setup > Connectors shows every connector's Status and Last Health Check. A connector that has not been checked for more than 7 days is marked as such: run Test again to refresh it.

More about testing and persisting: Testing and Persisting a Connector.


9. How files are added, and file rules

Web Storage (files)

  • Sending a file: export the schedule from Microsoft Project as a .mpp file. Open Files > Upload Files in the web app or the desktop client, and drop the file on the tab. The next Data Transfer sends it. The full steps are in Microsoft Project file transfers.
  • The file name must match the schedule. The name before .mpp must be exactly the schedule's name. Upper and lower case do not matter; spaces, hyphens and numbers do. Phase 2 Detailed.mpp matches the schedule Phase 2 Detailed, but not Phase2 Detailed.
  • One file per schedule. A new upload replaces the previous file for every Exchange Agreement that sends from that schedule.
  • Sharing fields: when you add a schedule with New MPP File, you can reuse another schedule's host fields. The choices are Add new host fields, Replace all host fields and Keep existing host fields.

SharePoint and Local File

  • Adding a file: save or copy the .mpp file into the folder. Then Persist again so that SchedEx creates its schedule.
  • The file name is the schedule. Phase 2 Detailed.mpp becomes the schedule Phase 2 Detailed. If you rename the file, SchedEx sees it as a new schedule.
  • Replacing a file: save the new version under the same name. The next transfer reads it.
  • Only the folder itself. SchedEx does not look in subfolders.
  • Keep only .mpp files in a SharePoint folder. With Local File, SchedEx skips other file types. With SharePoint, SchedEx reads every file in the folder, so other files can make the test or persist fail.

Every storage type

Rule Detail
Format Microsoft Project files with the .mpp extension only.
One project per file Each .mpp file is one schedule.
Size (web storage) Up to 100 MB per file.
Direction Send only. SchedEx does not write .mpp files.

10. Messages and what to do

While you fill in the wizard or save

Message What it means What to do
SharePoint URL is required The SharePoint URL is empty. Paste the folder's address.
Enter a complete address starting with https:// The address is not complete, or starts with http://. Copy the address again from the browser's address bar.
OneDrive addresses are not supported. Use a SharePoint document library or folder. You pasted a OneDrive address. Move the files to a SharePoint library and use its address.
That address is not on SharePoint Online… The address does not end in .sharepoint.com. Use your organization's SharePoint Online address.
Sharing links cannot be used. Open the folder in SharePoint and copy the address from the browser address bar. You pasted a link from Share or Copy link. Open the folder and copy the address bar instead.
SharePoint Client ID is required / SharePoint Tenant ID is required One of the two IDs is empty on one of the tabs. Fill in both, on each tab.
File system root folder path is required when using local file path File System Root Folder Path is empty. Enter the folder path.
Is that a file or a folder? The SharePoint address seems to end in a file name. Select Use this folder, or Keep what I entered if it really is a folder.
We couldn't add this connector. A Web Storage connector of this type is already set up for the … component, and only one is allowed per connector type and component. A Microsoft Project web storage connector already exists for this component. Use the existing connector, or choose SharePoint or Local File.
A connector with this URL or path already exists. Please update the URL or path and try saving again. Another Microsoft Project connector already uses this SharePoint address or folder. Use the existing connector, or a different folder.

When you test, persist or transfer

Message What it means What to do
Web storage configured. The web storage connector is set up correctly. Nothing. Create schedules with New MPP File.
No Microsoft Project file exists in the directory. Please verify and try again. Local File: the folder has no .mpp file. Save at least one .mpp file into the folder.
No Microsoft Project file exists in the SharePoint directory. Please verify and try again SharePoint: the folder is empty. Save at least one .mpp file into the SharePoint folder.
We couldn't find the selected directory. Please verify that it exists and is accessible. Local File: the path does not exist on this PC or server. Check the path, and that the network drive is connected.
We couldn't read from the selected directory because the app doesn't have permission… Local File: no read permission. Ask IT to give read access to the user or the Autonomous Component's account.
You or this application do not have access to … SharePoint refused access to the user or to the app. Ask IT to check the app's site access and the user's permissions. See Configure-SharePoint-Access.
Could not find a SharePoint site for '…'… The site in the address does not exist, or the app has no access. Check the address, then the app's site access.
The configured folder '…' does not exist in this document library… The folder was renamed, moved or deleted. Open the folder in SharePoint and copy its address again.
Success. The saved SharePoint address ends with the file name '…'… The test worked, but the saved address names a file. SchedEx used the folder. Edit the connector and save the folder's address to remove the warning.
The project file '…' could not be loaded. It may be missing or inaccessible… At transfer time, the .mpp file for the schedule was not found. Check that the file is in the folder (or uploaded, for web storage) under the schedule's name.
Unable to download file '…' from SharePoint… SharePoint: the file could not be read. Check the file exists, then run Test.
A message that the uploaded file does not match the schedule selected for the Exchange Agreement Web storage: the uploaded file's name does not match the schedule of the Exchange Agreement. Rename the file to the schedule's name plus .mpp.
Only .mpp files are supported for Microsoft Project source uploads. Web storage: the uploaded file is not a .mpp file. Save the schedule from Microsoft Project as a .mpp file.
Invalid Microsoft Project file. The file could not be parsed. Web storage: the file is damaged, or is not a real Microsoft Project file. Save the file again from Microsoft Project and upload it again.

11. Questions and answers

Can SchedEx write a Microsoft Project file? No. A Microsoft Project connector only sends. To receive a partner's schedule, use another connector on your side, for example an Excel connector.

I want automatic transfers from SharePoint. What do I need? Select Autonomous Component in Step 2. On its tab, choose Microsoft Entra ID App Certificate (SharePoint). IT must install the app's certificate on the Autonomous Component's server.

Can I change the storage type later? Yes. Edit the connector and choose another storage type. Then test again, and create the schedules again (Persist, or New MPP File for web storage). Check your Configs and Exchange Agreements afterwards, because the schedules may differ.

I added a new .mpp file to the folder. Why can't I select it in a Config? SchedEx only knows the files it found at the last persist. Run Persist again.

Do all my .mpp files need the same custom fields? No. Switch All files have same user fields off, and each file gets its own fields. Switch it on when the files share the same fields, so that one Config can cover them all.

The SharePoint password or app changed. What do I do? Edit the connector, update the Client ID or Tenant ID on each tab and save. Then run the test again. In the desktop client, signing out and in again makes SchedEx ask for a new Microsoft sign-in.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article