Contents
But after many publishes (I thing 30) SharePoint stop to changing workflow (I published it without any error and I can find new workflow release in SharePoint web interface). I published new version (with new commands) but workflow still use old one.
How does Microsoft Flow always run in context?
If your flow is running on an automated trigger then it will always run in the context of an owner of flow (Who created the flow). So that is who shows up in Modified By field in your SharePoint list. However the manually triggered flows, like the ones that start with a button in a PowerApp runs in the context of the user who presses the button.
Who is the Flow Creator in SharePoint list?
It is the default behavior that “Created By” or “Modified By” in SharePoint list will be the flow creator but not user who triggers the flow. You can still try ” Manage Run-Only Users ” but that only appears on manual triggers, such as Flow Button, SharePoint “For a selected item” and “For a selected file”.
Why is dynamic content not displaying in output-power?
The flow works in that the message is appropriately triggered, but the message posted is not rendering dynamic content as the expected values. Instead of seeing the name of the file in the created message, I’m seeing ” @ {triggerBody ()?
Is there a way to restore a previous version of workflow?
There is a little known way to go in and restore a previous version of your workflow. This uses the same versioning capability that lists and libraries have. By default, every time you publish changes to a workflow, they are saved as a new version.
Here’s how to revert to a previous version: In the left pane of SharePoint Designer, click the little pin icon next to All Files. Once All Files is expanded, scroll down and expand out your folder called Workflows. The workflow that I want to restore a previous version of is called “Check Audit Month”, so I’ll expand out that folder.
When do I publish a new version of SharePoint?
By default, every time you publish changes to a workflow, they are saved as a new version. This solution applies to all versions of SharePoint 2010, 2007, and SharePoint Online with Office 365.