Create a button to launch a Flow not working in list/library web part on page
Hello, although the functionality works to launch a flow with a button in the list/library itself, when you add the list/library on a page, the Flow button does not work! Even more, when you click the ellipsis menu, there is no Automate menu item.
If this is not a bug, but by design, this should at least be added to the page as a note
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: f60068c3-4534-a400-350b-fdbcefd684b6
- Version Independent ID: 228accdb-a7de-0671-34ad-60a37866c380
- Content: Use column formatting to customize SharePoint
- Content Source: docs/declarative-customization/column-formatting.md
- Product: sharepoint
- GitHub Login: @spdevdocs
- Microsoft Alias: spdevdocs
Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.
@thechriskent I believe this is the current intended behavior correct? As we don't have a launch panel on modern pages.
I can confirm that the Launch Flow and Edit Props actions don't work when using the list web part. I'd call that a bug since it wasn't called out as unsupported anywhere that I've seen. If it's by design, as @svanmoerkerke points out, it should be noted clearly as a limitation.
I see no reason why either of these actions shouldn't be supported (as a goal, no idea the tech constraints). If they aren't going to be supported then I'd love to see some additional context available as part of formatting. It would be great if we had a way of finding out where the format is being rendered so we could conditionally hide those unsupported features.
Any update/ workaround for this please?
Any solution for this?
I have the same issue with "EditProps" function on webpart. Are there any new information?
Hi, is there an update on this bug? For me it is still not working for flows and EditProps.
Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.
If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.
We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.