How To Build a Robust Power Pages File Attachment Pipeline with Microsoft Power Automate

This fileAttached object is then passed into the function that will handle sending it to your Power Automate flow (see attachFileToComment function above). The GUID for the related Portal Comment (Note) record is retrieved beforehand and supplied as part of that same call.

2. Building the Attachment Function

The function responsible for attaching the file performs several necessary tasks:

1. Accept the file and portal comment GUID as parameters
2. Convert the file into Base64 so it can be serialized and transmitted
3. Build the request payload with:
   • The Base64 file content
   • The Portal Comment GUID
   • The file name
4. Define the URL of the Power Automate flow that will receive the payload
5. Execute an AJAX POST to send the structured data to Power Automate

Converting the file to Base64 ensures the content can be safely serialized and transmitted to Microsoft Power Automate using standard request payloads, without relying on custom APIs or unsupported integration patterns.

3. Error Handling

Your JavaScript should also capture errors returned by the flow and surface them appropriately to the user interface. With this, the client-side portion of the solution is complete.

Power Automate: Handling the File Upload from Microsoft Power Pages

The Power Automate flow is responsible for receiving the input, storing the file in Dataverse, and returning a clean response back to Power Pages.

1. Accepting Structured Input from Power Pages

The flow begins with the Power Pages trigger, configured to accept three inputs:

• request – a container for request body metadata
• commentGUID – the Dataverse identifier for the Portal Comment
• fileName – the name of the uploaded file

2. Initializing a Standard Response Pattern

A single Compose action named response is added early in the flow.
Its structure is:

{ "status": "success" }

This creates a consistent, lightweight response definition that can be referenced at the end of the process.

3. Uploading the Attachment to Dataverse

The core step uses the Dataverse “Add a new file” action to store the uploaded content directly in Dataverse.

Configuration:

• Table: Portal Comments
• Row ID: commentGUID
• Column: Attachment
• Content: Base64 payload from Power Pages
• Content Name: fileName

By relying on Dataverse’s native file storage, this approach ensures:

• Proper file metadata handling
• Compatibility with large files
• Fewer permission-related issues
• Long-term sustainability compared to custom API endpoints

Using Dataverse’s native file capabilities also helps align file storage with existing security, governance, and data lifecycle practices already in place for the environment.

4. Sending the Final Success Response

Once the file is uploaded, the flow updates the response to:

{ "response": "Success" }

The return value(s) to Power Pages action then returns this structured message to the JavaScript caller.

Conclusion

This combination of JavaScript and Microsoft Power Automate provides a robust and maintainable pattern for handling file attachments in Power Pages. By clearly structuring requests, explicitly defining schemas, and leveraging Dataverse’s built-in file column capabilities, teams can improve reliability and scalability without introducing unnecessary complexity.

More importantly, this approach gives organizations a foundation they can standardize and build on as portal usage grows, requirements evolve, and user expectations increase, helping to ensure file attachments support the overall solution rather than becoming a recurring point of friction.