On This Page
Overview
The Autodesk BIM 360 connector in DryvIQ allows you to analyze, migrate, copy, and synchronize files between your Autodesk BIM 360 account and cloud storage repositories and 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.
Creating a Connection
Expand the Manage section in the left navigation menu.
Click Connections.
Click 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 click Sign In.
Click Allow access when prompted to authorize the connection.
You will see a green "Connected” message on the bottom of the modal when DryvIQ establishes connection. (If the connection test fails, verify the information you entered.)
Click Done.
Add connection modal for Autodesk BIM 360 (OAuth 2.0)
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 you add a custom name if you will be creating multiple Autodesk connectors you need to readily identify. | 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. This value will be provided by your administrator. | Optional |
Client Secret | This field displays only when you select Use custom client credentials. This value will be provided by your administrator. | Optional |
Autodesk Sign In
Authorize Application
Features and Limitations
Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms and allows 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.
Supported Features | Unsupported Features | Other Features/Limitations |
|---|---|---|
File size maximum: N/A | ||
Timestamp preservation | Invalid characters: \ / < > : " | ? * ` \n \r \t \f ¢ ™ $ ® | |
Author/Owner preservation | Path length maximum: 255 | |
Segment path length: N/A | ||
Restricted types: N/A | ||
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 does not impose restrictions for the total path length.
Segment path lengths are limited to 255 character. Segments are delimited by a forward slash (/). For example, <max 255 characters>/<max 255 characters>.
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.