File Uploads: Azure Storage, Multiple Files, and Server Paths

MegaForm supports multiple files in one File Upload field and can store them through DNN's Folder Provider. If that DNN folder is backed by Azure Storage, MegaForm uses the existing DNN Azure connection; MegaForm does not need a second Azure SDK or a second set of Azure credentials.

This page answers four common questions:

• Can MegaForm upload files to Azure Storage? Yes, through DNN Folder Provider.
• Is private storage the only option? No. On DNN, choose DNN Folder Provider to use the site's configured folder mapping.
• Can one field accept several files? Yes. Set Max files to a value greater than 1.
• Is a separate server path saved for each file? Yes. Each uploaded file keeps its own stored reference and server path.

Choose the primary storage route

Open MegaForm → Settings → Upload Settings.

The two primary storage modes are:

For an existing DNN Azure connection, select DNN Folder Provider and enter a logical DNN folder such as MegaForm/Uploads. This is not a Windows path and it should not contain a drive letter.

The resulting route is:

File Upload field → DNN logical folder → DNN's configured provider

If DNN maps that folder to Azure, the file goes to Azure. If DNN maps it to the normal portal file system, the same MegaForm configuration writes there instead.

MegaForm's Cloud Storage page is different. It creates optional Google Drive or Amazon S3 connections that can receive a copy after submission. It is not required for the primary DNN/Azure route.

Configure a field for multiple files

In Form Builder:

1. Add or select a File Upload field.
2. Open Edit settings for that field.
3. Expand File Settings.
4. Set Max files to a number greater than 1.
5. Set Max size (MB) and Allowed extensions.
6. Save and publish the form.

The global upload policy is still the ceiling. A field cannot bypass the global file-size or extension restrictions, and blocked executable or script extensions remain rejected.

What the visitor sees

When Max files is greater than 1, the browser file picker accepts multiple files in one selection. The field lists each file separately and shows the upload result for each item.

The form should not be considered submitted until every selected file has finished uploading. If one file fails validation, correct that file and try again; the error belongs to that item, not to an invisible combined upload.

Verify every saved path

After submission, open Submissions, select the record, and inspect the File Upload field. Every file is shown as a separate item with its own file name, size, stored reference, and server path.

With DNN Folder Provider, a path can look like:

MegaForm/Uploads/form-242/field-file_upload/example-uniqueid.txt

The internal stored reference can look like dnnfile:173. That reference lets MegaForm ask DNN for the file without assuming whether DNN keeps it on a local disk or in Azure.

For Azure-backed folders, the displayed server path is therefore a DNN-relative path, not an absolute Windows path. This is expected and keeps the submission portable across DNN storage providers.

Visual QA result

The current DNN build was tested end to end with a File Upload field configured for five files:

• The public input exposed native multiple-file selection.
• Two text files were selected in one chooser and both reached the uploaded state.
• The form submitted successfully.
• Submission details showed two file rows.
• Each file had a different DNN file reference and a different server path.
• Both paths existed under the configured DNN folder on the test site.
• No JavaScript console errors were recorded during the tested flow.

The test site used DNN Folder Provider backed by its normal portal folder. The same MegaForm route is designed to use Azure when the selected/default DNN folder provider is Azure-backed. A real Azure transfer still depends on a valid Azure Folder Provider configuration in DNN.

Troubleshooting checklist

If only one file can be selected:

• Confirm Max files is greater than 1 in the field's File Settings.
• Save and publish after changing the field.
• Reload the public form without an old cached script.

If a file is rejected:

• Compare its extension with both the field-level list and the global Upload Settings.
• Check the field and global maximum size.
• Do not add executable or script extensions to a public form.

If you expected Azure but files use local storage:

• Confirm MegaForm's primary Storage Mode is DNN Folder Provider.
• Confirm the logical DNN folder is assigned to the intended Azure-backed provider in DNN.
• Test the DNN folder independently; MegaForm deliberately follows DNN's mapping rather than storing Azure credentials itself.

If the server path is missing:

• Open the newest submission and expand the File Upload value.
• Confirm the form was republished after File Settings changed.
• Verify that all uploads completed before Submit.
• Record the submission ID and file name when asking for support.

For a broader overview of storage and external services, continue with Storage & Integrations.