What Is an External Data Source in CDEAdminTools?

Modified on Wed, 26 Nov at 9:36 AM

1. Introduction

In CDEAdminTools, a Data Source represents a connection between CDEAdminTools and an external system outside Autodesk.

This external system can be, for example:

  • A SharePoint site

  • A shared folder in OneDrive

  • A shared folder in Google Drive

  • An SFTP server

  • A custom or proprietary document repository managed by the customer

This article explains what an external Data Source is, what it is used for, and how it fits into the overall synchronization model with Autodesk projects.
It is informational only and not a step-by-step setup guide.


2. What Is an External Data Source?

A Data Source defines the connection configuration to the “other side” of a synchronization, i.e., the non-Autodesk system.

Each Data Source includes, among other things:

  • The type of external system (SharePoint, OneDrive, Google Drive, SFTP, custom, etc.)

  • The connection details (URL, host, credentials, scopes, etc.)

  • The authentication method required by that external system

You can have one or multiple Data Sources, either:

  • Of the same type (e.g., several SharePoint sites), or

  • Of different types (e.g., one SharePoint site, one Google Drive folder, one SFTP server, etc.)

This gives you flexibility to connect CDEAdminTools to all the repositories that are relevant to your document workflows.


3. What Is Synchronized Through a Data Source?

Regardless of the external system type, CDEAdminTools focuses on synchronizing:

  • Folders

  • Documents/files

If the external system supports versioning, CDEAdminTools will also aim to preserve document versions so that changes are properly tracked on both sides.

The goal is to keep the folder structure and documents aligned between Autodesk and the external repository, according to the synchronization configuration.


4. One-Way vs Two-Way Synchronization

Synchronizations involving a Data Source can be configured as:

  • One-way (unidirectional)

    • Autodesk ➝ External Data Source

    • External Data Source ➝ Autodesk

  • Two-way (bidirectional)

    • A “mirror” configuration where both sides are kept aligned as closely as possible

This allows each customer to choose the synchronization pattern that best fits their process:

  • Use Autodesk as the source of truth and push changes to the external system

  • Use the external system as the source of truth and push changes back into Autodesk

  • Or configure a full mirror so that both ends share the same structure and documents


5. How Data Sources Work Together with Sync Projects

The Data Source itself only defines how to connect to the external system.
The actual synchronization logic is defined in a separate concept: the Sync Project.

A Sync Project in CDEAdminTools links:

  1. An Autodesk account and project, plus a root folder inside that Autodesk project

  2. An External Data Source, plus a root folder inside that Data Source

Once a Sync Project is configured:

  • Any changes that occur in the selected Autodesk project are synchronized in real time to the external Data Source (for Autodesk ➝ external direction).

  • If the synchronization is configured in the opposite direction (external ➝ Autodesk), those changes are updated periodically at a defined interval. We are also working on enabling this direction in real time in future versions.

In summary:

  • The Data Source defines how CDEAdminTools connects to the external system.

  • The Sync Project defines both ends of the bridge:

    • The Autodesk side (account, project, root folder)

    • The external side (Data Source and root folder)


6. When Should You Create Multiple Data Sources?

You might want to configure multiple Data Sources in scenarios such as:

  • Different business units or projects use separate SharePoint sites or drives

  • You need to synchronize Autodesk projects with multiple external destinations (e.g., SharePoint + SFTP)

  • You want to isolate credentials or access rules per repository or client

  • You manage multiple environments (e.g., internal repository vs. client-facing repository)

Having multiple Data Sources helps keep configurations clean, secure, and easier to manage.

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