SharePoint Button Web Part "Run Flow" Action Only Works in the Default Environment
Hello! I was setting up a new workflow for a customer and encountered a limitation with the button web part's "Run Power Automate Flow" option. Background The SharePoint Button web part has a built-in action type: Run Power Automate Flow, which accepts a Flow ID. This is a clean option for giving users a one-click way to trigger an instant/manual flow directly from a SharePoint page. The Finding When configuring the Button web part with Run Power Automate Flow, it appears that the flow must reside in the Default Power Platform environment for this action to work. Flows in non-default (department-level) environments fail silently with the following error: Could not find flow '<flow-id>'. Testing Approach To isolate the variable, I did the following: Took an existing instant flow and exported it from a department-specific environment, then imported a copy into the Default environment — so the logic was identical. Created two Button web parts on the same SharePoint page: Button A → Flow ID from the department-level environment copy Button B → Flow ID from the Default environment copy Both buttons were configured identically, with the only difference being which environment hosted the flow. Result: ✅ Button B (Default environment) — triggered successfully ❌ Button A (department-specific environment) — returned "Could not find flow '<id>'" The account I used for testing is the same one that created the workflows and also has site collection admin rights, so permissions should be a factor. Related Behavior This appears to be consistent with a known behavior of running an instant flow from a SharePoint list (from the List menu , "Integrate" -> "Flows" -> <workflow name>), where instant flows with manual SharePoint triggers must also reside in the Default environment to function correctly. Both surfaces appear to share the same environment scope constraint when resolving flows by ID from a SharePoint context. Questions for the Community / Microsoft Is this a documented platform constraint for the Button web part's Run Power Automate Flow action? Is this constraint expected to change, or is it by design? Workarounds In this case, I found two decent workarounds: Instead of configuring the Button web part action as Run Power Automate Flow, it can be configured as Open Link, and then use the flow's direct run URL: https://make.powerautomate.com/environments/<environment id>/flows/<flow id>/run Also using the direct run URL, enter that into a navigation link or regular hyperlink on the SharePoint page to launch the workflow run page. Any insight from the community or the product team would be appreciated — especially if there's a documented reference I may have missed. Thanks!
Create reference number in SharePoint lists with each new entry
Migrating an Excel table into SP lists, so I can existing reference numbering system, so with each new entry I need this to increase by one. Let's say the current ref number is R5687 how to I ensure that subsequent entries are allocated a reference number, which is one more last the last
Export and Import Modern Sharepoint list
Hi all, I have created a PowerApps custom form on Sharepoint list on our dev environment. What is the best way to import this list to different environment (etc. production)? I would guess is should be done by creating list template and import it to new environment. Does anyone have experience with importing sharepoint list with powerapps custom form? Thanks a lot, PeterImport list from excel/csv people picker field
I have an existing list that I want to export and import into a different site. The issue is, there are several people picker columns on this list and they are consistently being imported as text fields instead of a people picker column. The export is seemingly fine, but the import is not recognizing these columns as their original type - people. Any tips or suggestions?Private drafts stay private even after publishing
If one of our authors makes a private draft and sends it for approval for publishing, it remains private even after approving. The only workaround I can find is to create a new page from scratch, copy the content across and delete the private draft. Surely this isn't how it's meant to work? Am I doing something wrong or is something broken? We are using https://support.microsoft.com/en-gb/office/approval-flow-for-modern-pages-a8b2e689-d4a1-4639-8028-333c0ece30d9.
Users unable to determine who has access to document library due to security groups
Greetings, Maybe I went about this the wrong way. Looking for advice on either the proper way we should be moving forward on this or any other comments or insight we should be considering. This is for SharePoint online via Microsoft 365 Business license. Scenario: 1. SharePoint Document Library per department (Each Document Library exists in its own SharePoint site), essentially being used as a company drive. 2. Some users should only officially have access to specific folders in some of the document library. 3. If say a person in accounting has access to some specific folders, and either they are replaced or a new accounting user comes in.... should be able to reference the access the existing person has in order to give the same access to the new user. 4. Common Request: Give UserB the same folder access as UserA. 5. Some users should have access to the entire document libraries while other users only have access to specific subfolders. Current Implementation: 1. In Entra, created Security Groups that tied to specific folders. -- For Example for the accounting folder, only management has access to the entire folder but the accounting staff only have access to specific folders. So like there is a FiscalYear2024 folder, so I created a security group called sec-Accounting-FiscalYear2024 and assigned the members that should only have access to that folder and not the rest of the library. -- My thought behind this was if a new user was replacing the existing user or joining the department, I can just reference the existing user security group membership and copy it to the new user. 2. In the SharePoint document Library, I create a shareLink that is assigned to the security group I made for that access. Then I give that link to the users I assigned the membership to. Current Issue: 1. Aside from the official document sharing/access that is being done from the security groups above. There are occasions where users of a sharepoint need to share specific files or folders to other users. 2. However, they are all panicking and confused because aside from themselves they are unsure who has access to the existing folders/files in the document library. 3. When going to manage permissions of a file/folder, it only shows the group assigned to it but not the members of the group. 4. So since users can't see the members of the group assigned to a folder, they have no idea who has access to that folder and are getting confused. If this was an NTFS drive, it would be super easy for users to see who has access and etc by looking at the properties but I'm stuck behind some limitations of sharepoint I didn't realize existed until I tried to implement certain workflows. Any advice here would be greatly appreciated, as my implementation has turned into a point of frustration for end users. Thank you in advance!
Automatically email supplier when their certificate expires
Good afternoon. I have set myself a challenge and really could do with some help. I have a list of suppliers like below. I have expiry dates set up, with a colour formatting to show any date past the current date. On the end of the row, there is an email address of the company contact. I want SharePoint to automatically email that person as soon as it turns red/expires. What is the simplest way of doing this? I have looked at Flows etc, and online on video tutorials, but some of the guides are old and out of date or very complex and I am a novice. Is anyone kindly, can give me a step-by-step guide on how to do this, as this would be just awesome and finally bring my company into the 21st century! Thanks in advance.
SharePoint List Web Parts - New UX
Hey everyone, I am hoping I can get some assistance on the following request. My organization's using SharePoint to manage multiple processes, but am confused with a new UX update that's come in the last few days. Please look at the following example, which is a list with a modern calendar view: For all of my lists, that are used as a web part on a different Site Page, have been given an ability to add a 'New Item', by selecting the title name, which's very frustrating as all of our list processes already have their own system to collect information and it seems as though I cannot turn off this functionality. Any help would be very much appreciated.
