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

Microsoft Power Automate – Support for normalized schema import for data ingestion

We are announcing the ability to ingest data in a normalized data structure format for process mining in Power Automate. This feature will rea...

1 hour ago

Power Automate – Analyze your processes in the process intelligence experience

We are announcing the ability to analyze your processes in the process intelligence experience in Power Automate. This feature will reach gene...

1 hour ago

Power Platform Fundamentals #5: Building Your First Canvas App in Power Apps: Step-by-Step Guide from Setup to Deployment: Quick Read Series

Introduction Organizations today need quick, user-friendly business applications that can be built rapidly without heavy development effort. T...

6 hours ago

Power Automate: Planner - Update a task (V2) Action

The 'Update a task (V2)' Planner action upgrades Power Automate with Percent Complete, Bucket Id, and 25 category fields, plus key Preview got...

10 hours ago

Power Automate Agent Flows: The Smarter Way Businesses Are Automating Decisions in 2026

If your business is still waiting on manual approvals, forwarded emails, or spreadsheet updates after every meeting, there is a cost to that d...

12 hours ago

SharePoint: Power Automate trigger and action for forms in SharePoint

We are introducing new Power Automate integration capabilities for forms in SharePoint, enabling customers to create automated workflows based...

14 hours ago

Power Automate: take Function

Learn how to use the "take" function in Power Automate. Grab items from the front of arrays and strings, handle edge cases, and combine with s...

1 day ago

Variables inside Apply To Each steps in Power Automate

For many years I’ve been saying, don’t use variables in Power Automate as it hurts the flow’s performance. Recently it was p...

1 day ago

Power Automate trigger and action for forms in SharePoint (Preview)

Power Automate introduces preview triggers and actions for SharePoint forms, enabling workflow automation on form submissions starting May 202...

1 day ago

Generate documents using forms in SharePoint with Power Automate (Preview)

Power Automate will introduce a preview action in May 2026 to generate documents from SharePoint forms by mapping inputs to templates. Availab...

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