Power Pages: Build Forms & Attach Files

Key insights

• Power Pages basic forms: Low-code web forms that publish Dataverse forms so users can create, view, or update records directly from a site.
  They let makers expose existing Dataverse fields and layouts without custom development.
• File attachments: Add an upload control to a form to accept files, show upload progress, and let users delete or download attachments.
  You can restrict accepted MIME types and choose single- or multi-file uploads for each form.
• Azure Blob Storage: Use Azure Blob Storage for large or high-volume files — Power Pages supports uploads up to 10 GB when Blob storage is configured.
  Alternatively, small or simple scenarios can store files as Dataverse note attachments.
• Dataverse integration: Submitted data and attachments write directly to Dataverse, making records immediately available to Power Automate, Power BI, model-driven apps, and other platform tools.
  This streamlines workflows and reporting.
• Attachment configuration: Typical steps include selecting a Dataverse table and form, adding the basic form to a page, enabling Attach File, choosing storage, allowing multiple files, and setting accepted file types.
  Always test the full user journey after configuring permissions.
• Security and API: Configure table and annotation permissions so users can create and manage attachments safely; later portal versions may not require enabling table permissions just to attach files, but proper access rights remain essential.
  For custom experiences, use the Web API to view, upload, edit, or delete files stored in Blob storage.

Overview of the video

The recent Pragmatic Works live episode in the "Learn With The Nerds" series walks viewers through getting started with Power Pages, focusing on basic forms and file attachments. The hosts demonstrate how to stand up a site, wire it to Microsoft Dataverse, tighten security, and deliver an experience that end users can actually use. They highlight practical scenarios such as service requests, applications, and supplier onboarding where form attachments add real value. Consequently, the video aims to help both beginners and intermediates move from setup to production-ready patterns.

How attachments work and how to configure them

In the demonstration, the team explains that a basic form on Power Pages ties together three parts: a Dataverse table, a Dataverse form, and the Power Pages basic form component that publishes the form to a site. They show makers how to add an upload control, set accepted MIME types using the Accept setting, and choose whether to permit multiple files via the Allow Multiple Files option. The step-by-step configuration covers selecting storage location, enabling file attachment, and testing the full submission flow so that files land where expected.

The presenters also run through the typical setup sequence: prepare the table and form in Dataverse, add the form to a page, enable the Attach File control, and then set storage and upload rules. They emphasize defining accepted file types and testing uploads with user accounts to ensure permissions behave as intended. As a result, viewers get a clear, repeatable checklist for delivering a basic file-enabled form on a portal.

Tradeoffs: storage choices, performance, and cost

The video contrasts two storage options for attachments and explains the tradeoffs between them. Storing files as Note Attachment keeps everything inside Dataverse and simplifies permissions and integration, but it can be costly and is less suitable for very large or high-volume files. Conversely, redirecting attachments to Azure Blob Storage supports files up to 10 GB, reduces pressure on Dataverse storage, and scales for media or engineering assets, yet it introduces additional configuration and potential cloud storage costs.

Furthermore, the hosts discuss user experience tradeoffs: the newer upload control shows progress and file sizes, which improves usability, but supporting large uploads requires more attention to network reliability and timeout handling. They also note that choosing Azure Blob Storage often means investing time in configuring secure access and lifecycle policies, so organizations must weigh upfront setup work against long-term storage savings and performance. Ultimately, the right choice depends on file size distribution, expected volume, and budget.

Security, permissions, and operational challenges

Security receives strong focus in the episode because attachments intersect with table permissions, portal access, and storage security. The presenters explain that basic attachment capability does not necessarily require enabling table permissions on the form in newer portal versions, but it does require properly scoped create and read rights for the related entities, including the annotation table. As a result, teams must plan and test permissions thoroughly to avoid exposing files or preventing legitimate uploads.

They also point out the operational hurdles of managing MIME restrictions, virus scanning, and retention. Setting strict Accept types reduces risk but can frustrate users if legitimate formats are omitted, while allowing broad types increases security work downstream. Additionally, when using cloud storage, teams must secure blobs with appropriate access controls and consider automated cleanup or archival to control long-term costs and compliance risks.

Practical recommendations and next steps

The Pragmatic Works hosts offer pragmatic next steps for makers who want to adopt file-enabled basic forms. They recommend starting with conservative MIME restrictions, testing uploads across typical user scenarios, and instrumenting the flow so errors and permission issues surface quickly during QA. Accordingly, teams should also define expected file sizes and volumes early to choose between Note Attachment and Azure Blob Storage and to plan for costs and governance.

Finally, the video highlights extensibility paths for complex needs: use the Web API to build custom file experiences, integrate with Power Automate for processing, and add lifecycle policies for blob data. While customizations add development overhead, they deliver richer user interfaces and tighter control, so organizations should balance speed of delivery with long-term maintainability. Overall, the episode gives a clear roadmap that balances configuration simplicity against operational and security tradeoffs, helping teams move from proof-of-concept to production with measured confidence.

Keywords

Power Pages basic forms, Power Pages file attachments, Power Pages forms tutorial, Power Pages attach files, Power Pages form customization, Power Pages upload files, Power Pages attachment best practices, Power Apps portals file attachments