Loading...

Managing Public SharePoint Documents for Power Apps Portal and Internal Documents Using Cloud Flow (Part 8 of 8)

Managing Public SharePoint Documents for Power Apps Portal and Internal Documents Using Cloud Flow (Part 8 of 8)
This is the eighth post in a series of Automating SharePoint Integration with Dataverse using Power Automate. You can check out the other posts via these links (Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7)

Power Apps portal has the capability to upload and display documents to and from SharePoint directly to the Document Library related to a record. But sometimes, there is a requirement to manage two types of documents, one for the public documents visible to the portal user and the private documents which are supposed to be visible only for the internal Dynamics 365/Power Apps users. This can be achieved by uploading the public documents for the portal user to the Document Location which is created first and the private documents for the internal users can be uploaded to the second Document Location. (Special thanks to Gus Gonzalez for sharing this solution by Nicholas Hayduk.)

We can automate this solution by automatically creating the x2 Document Locations with a cloud flow as soon as the record is created. In the Part 1 post, I have explained how to automatically create SharePoint Document Location OnCreate of the record. This is the extension the previous solution with the additional steps to create the second Document Location.


These are all the steps included in the cloud flow for this solution. The following cloud flow is triggered on create of the Contact and creates the public Document Location for the portal user as in the Part 1 post and then, creates the private Document Location for the internal users.

The first part of the cloud flow is almost the same as the the Part 1 post except the SharePoint folder path and Relative URL with "_Public" postfix (as highlighted in the screenshot above).

After creating the first Document Location, delay the flow for 5 seconds to make sure that the timestamp of the second Document Location is different from the first one. The steps for creating a SharePoint folder and Document Location are almost exactly the ones as the public one except the "_Private" postfix (as highlighted in the screenshot).


After creating two Document Locations, the documents uploaded to the first Document Location (red highlighted ones) can be visible on the portal and the documents uploaded to the second Document Location (green highlighted ones) can be visible only to the internal Dynamics 365/Power Apps users. 

The user can see the documents from both location by manually selecting "All Locations" from the Document Location menu but that selection cannot be default. When the internal user opens the Documents tab, the Document Location in the first menu item is shown (e.g. Private Documents in this case when the Document Location name is sorted alphabetically).


Summary

When the SharePoint integration from Power Apps portals is enabled, the users can see all the SharePoint documents related to the record but we can upload the documents for internal purpose to the secondary Document Location and keep those hidden from the Portal user.

Published on:

Learn more
Linn's Power Platform Notebook
Linn's Power Platform Notebook

A blog about Dynamics 365 and Power Platform (canvas apps in Power Apps and flows in Power Automate).

Share post:

Related posts

Extending Power Automate Run History Beyond 28 Days Using Cloud Flow Run Metadata

Power Automate has become the backbone for many business processes, integrations, and automation scenarios across the Power Platform ecosystem...

2 days ago

Power Automate – Restore accidentally deleted flows

We are announcing the ability to restore accidentally deleted flows in Power Automate. This feature will reach general availability on July 30...

3 days ago

Power Automate – Review Firewall Configuration for Upcoming Platform Infrastructure Updates

We identified that one or more flows in your environment may be affected by existing firewall or IP allow list configurations. What action do ...

3 days ago

Power Automate – Export work queue items to CSV

We are announcing the ability to export work queue items to CSV in Power Automate. This feature will reach general availability on July 31, 20...

3 days ago

Power Automate – UI automation repair agent

We are announcing the UI automation repair agent in Power Automate. This feature will reach public preview on July 16, 2026. How does this aff...

3 days ago

Power Automate – View machine and flow utilization in dashboards

We are announcing the ability to view machine and flow utilization in dashboards in Power Automate. This feature will reach general availabili...

3 days ago

Power Automate – Build better forms with integrated Power Apps

We are announcing the ability to launch interactive Power Apps directly from desktop flows within Power Automate. This feature will reach gene...

3 days ago

AI-Assisted Power Apps Code App Development Using GitHub Copilot CLI

Power Apps Code Apps bring modern web application development into the Power Platform ecosystem by combining React-based applications with Dat...

4 days ago

Power Automate: isInt function

Checks if a string is an integer.

5 days ago

Dynamics 365 Attachment Offloading: Power Automate vs. Dedicated Solution

  TL;DR 30-second summary Dynamics 365 stores attachments in the Dataverse by default. Thatโ€™s fine... until it isn't. As your file storag...

5 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy