...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
On
...
This Page
| Table of Contents |
|---|
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.
Create Connection |
...
User Interface
Select Connections > Add connection.
Select Autodesk
...
BIM 360 as the platform on the Add connection modal.
Enter the connection information. Reference the table below for details about each field.
Test the connection to ensure
...
DryvIQ can connect using the information entered.
You will see a "Connection test succeeded" message on the Add connection modal when DryvIQ establishes connection. (If you don't see this message, verify the information you entered.)
Select Done.
Add connection modal - Autodesk
...
BIM 360
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.” |
...
DryvIQ recommends you add a custom name if you will be creating multiple |
...
connectors you need to readily identify. | Optional | |
Client ID | Enter the client ID that needs to be used to access the platform. | Required |
Client Secret | Enter the client secret that needs to be used to access the platform. | Required |
Account ID | Enter the account ID for the account that needs to be accessed. | Required |
Region | Select the region: US or EMEA. | Required |
Connection Test Succeeded
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.
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 |
|---|---|---|
...
...
Timestamp preservation | Invalid characters: \ / < > : " | ? * ` \n \r \t \f ¢ ™ $ ® |
...
Author/Owner preservation |
...
255 | ||
Segment path length: 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.
Create Connection | REST API
Create a basic Autodesk connection using the sample POST below. Replace the “name” and “auth” values with the values that apply to your
...
Autodesk connector.
POST {{url}}v1/connections/ | ||
|---|---|---|
|
...
|
...
|
Create a Job |
...
REST API Job Configuration Example
The sample code below shows how to create a job for an Autodesk connection created to connect as a standard user.
| Note |
|---|
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 | ||
|---|---|---|
|
...
|
...
|