Supported File Types and Limitations

Supported File Types

The Bulk Upload Tool supports the same file types supported in the Files tool. See Supported Files on Web to see supported, viewable, and unsupported file types.

Note: For the Files with references workflow, you can exclude unsupported file types and other files from upload. See Export JSON from DWG Migration and Integrity for Docs Tool for details on how to exclude specific file and file types from the JSON file.

Limitations

The files and folders for upload need to adhere to the following Files tool limitations or they will fail in the validation step. This will result in validation errors and the upload will not be permitted.

The Bulk Upload Tool has only been tested on Microsoft Windows versions 10+.
Each upload needs to include at least one file.
You can't upload to a folder with a naming standard applied.
No progress bar on estimated time remaining.
Nested file references may not upload properly.
Validation only checks the local source folder and subfolders. If the contents of the target folder, relevant Deleted items, and Holding area in Docs makes the upload exceed the limitations, the upload will pass the validation check but fail on upload.
Maximum 20,000 items (folders and files) per folder.
Maximum 25 tiers of subfolders.
Maximum 48 GB size per file. There is no restriction on the total upload size.
Maximum 50,000 files per upload.
Maximum 200 references per file.

Known Issues

You may have port conflicts which prevent the Bulk Upload Tool from working or displaying properly.

Port usage and network access

The Bulk Upload Tool requires the following local ports to be available when running:

Port 3000: User-facing frontend.
Port 8083: API services and administrative tools (Hangfire).

Both ports also need to be allowed access through firewalls in production environments.

Port conflicts

The Bulk Upload Tool will not work or display properly if either port is already in use. This occurs because:

Both services are required for full functionality.
The Frontend can't communicate with backend if ports conflict.
Proxy configuration requires specific port mapping.

Troubleshooting

If the application fails to start:

Check if another process uses ports 3000 or 8083.
Use netstat -ano | findstr :3000 and netstat -ano | findstr :8083 (Windows)
Stop the conflicting processes.