Overview

The Autodesk BIM 360 connector in DryvIQ enables you to analyze, migrate, copy, and synchronize files between your Autodesk BIM 360 account and cloud storage repositories, as well as on-premise network file shares. The first step is to create the Autodesk BIM 360 connection by providing the connection information required for DryvIQ to connect to the platform. The connector can be created using any user account with permissions to access the content.

Creating a connection using OAuth 2.0 authentication requires different information than connecting to an account that doesn’t use this authentication. Review the table below to ensure you have the information required to create the connection.

Adding the DryvIQ App

You must add the registered DryvIQ app to your Autodesk BIM 360 account before you create a connection in the DryvIQ Platform. You will not be able to successfully create a connection if you do not add the app.

Log in to your Autodesk BIM 360 account as the Account Administrator.
Click Apps on the top menu bar.
Locate and select the SkySync app (DryvIQ’s previous name).
The “SkySync” app page displays.
Click Add to BIM 360.
Click Authorize to grant DryvIQ access.
You can proceed to creating the connection in the DryvIQ Platform.

Create Connection | User Interface

Select Connections > Add connection.
Select Autodesk Data Management (OAuth 2.0) as the platform on the Add connection modal.
Enter the connection information. Reference the table below for details about each field.
Select Sign in with Autodesk Data Management (OAuth 2.0).
On the Sign In modal, enter the email address and click Next.
Enter the password and select Sign In.
Select Allow access when prompted to authorize the connection.
You will see a green "Connected” message at the bottom of the modal when DryvIQ establishes a connection. (If the connection test fails, verify the information you entered.)
Select Done.

Add Connection Modal - Autodesk BIM 360 (OAuth 2.0)

Field	Description	Required

Field	Description	Required
Display as	Enter the display name for the connection. If you will be creating multiple connections, ensure the name readily identifies the connection. The name displays in the application, and you can use it to search for the connection and filter lists. If you do not add a display name, the connection will automatically be named “Autodesk BIM 360 (OAuth 2.0).” DryvIQ recommends adding a custom name if you will be creating multiple connectors that you need to identify easily.	Optional
Platform API client credentials		Required
Use the system default client credentials	Select this option to use the default DryvIQ client application.
Use custom client credentials	Select this option to use custom client credentials provided by your administrator. When selected, two additional fields will be available to enter the credentials.
Client ID	This field displays only when you select Use custom client credentials. Your administrator will provide this value.	Optional
Client Secret	This field displays only when you select Use custom client credentials. Your administrator will provide this value.	Optional

Autodesk Sign In

Authorize Application

Connection Test Succeeded

Features and Limitations

Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms, allowing you to configure actions based on Job Policies and Behaviors. The information below is platform-specific. Use the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.

Files and Folders

Below is list of supported and unsupported features as well as additional file/folder restrictions for the Autodesk BIM 360 connector.

Supported Features	Unsupported Features	Other Features/Limitations

Supported Features	Unsupported Features	Other Features/Limitations
Version preservation	File lock propagation	File size maximum: N/A
Timestamp preservation See below for more information.	Mirror lock ownership	Invalid characters: \ / < > : " \| ? * ` \n \r \t \f ¢ ™ $ ®
Author/Owner preservation See below for more information.	Account map	Path length maximum: N/A (See Path Lengths below)
	Group map	Segment path length: 255 (See Path Lengths below)
	Permission preservation	Restricted types: N/A
	User impersonation
	Metadata map
	Tags map

Author/Owner Preservation

When Autodesk BIM 360 is the destination platform, author/owner preservation is not supported.

When Autodesk BIM 360 is the source platform, author/owner preservation is supported only for destination platforms that support this attribute.

Path Lengths

Autodesk BIM 360 does not impose restrictions on the total path length. However, segment path lengths are limited to 255 characters. Segments are delimited by a forward slash (/). For example, <max 255 characters>/<max 255 characters>.

Path Requirements

When the Autodesk BIM 360 connection is the destination connection for a migration project, you must select the “Project Files” folder or deeper as the destination path. Attempting to use a path above the “Project Files” folder will result in an error similar to, “New files must be created within an existing project folder.”

Timestamp Preservation

When Autodesk BIM 360 is the destination platform, timestamp preservation is not supported.

When Autodesk BIM 360 is the source platform, timestamp preservation is supported only for destination platforms that support this attribute.

Create Connection | REST API

The following GET will return a target URL. Use this URL to log in to your Dropbox for Business account and authenticate the connection. Make sure you connect using an Administrator account.

Create New Autodesk Data Management Connection using OAuth 2.0

Create New Autodesk Data Management Connection using OAuth 2.0
GET {{url}}v1/connections/platforms/autodesk-bim360-oauth2/new

Create a Job | REST API Job Configuration Example

The sample code below demonstrates how to create a job for an Autodesk connection established as a standard user.

When creating a job with Autodesk, you must select the project and then the project directory when configuring the job location paths in order to transfer content. Otherwise, the job will fail with an "Unknown failure" error.

POST {{url}}v1/jobs

POST {{url}}v1/jobs

{
    "name":"Simple Job",
    "kind": "transfer",
    "transfer": {
      "transfer_type": "copy",
        "source": {
            "connection": { "id": "Source connection ID" },
            "target": {
                "path": "/sourceDocumentLibrary"
            }
        },
        "destination": {
            "connection": { "id": "Destination Connection ID" },
            "target": {
                "path": "/destinationFolder"
            }
        },
        "simulation_mode": false
    },
    "schedule": {
        "mode": "manual"
    },
    "stop_policy": {
        "on_success": 5,
        "on_failure": 5,
        "on_execute": 25
    },
    "category": {
      "name": "Report {Name}"
    }
}