This has been a matter discussed in Microsoft's Power Users Community within several threads. A concluding topic, save an email to a document library, sheds some light for how you may actually succeed with your requirement.
As using Flow's functionality to re-attach email's attachments to a new file seemingly just does not work, you can achieve the same ...
Would Created != Modified work? Something like this:
"Yes" in this scenario would be modified (its a not). You can just adjust accordingly.
SPD is still supported with SharePoint 2016. Mainstream support ends in 2021, and extended support ends in 2026. So one answer is to keep maintaining existing workflows in 2013, and look into the new tools for new solutions. (if you're concerned about the 2021 date, then you should already be concerned that the end of mainstream support for 2013 has already ...
I don't know if it's possible, but you could use flow itself to export and import flows. And maybe you could build a loop to deploy it to several libraries with the library as parameter.
This post describes options to extract and deploy flows with flow: http://johnliu.net/blog/2017/12/you-must-copy-all-your-flows-to-sharepoint-simple-ideas-are-the-most-...
You would need to make a "shadow" field which you compare to see if an email has been sent already.
So create a boolean field called MailSent, default it to "No". Now change your flow to make it only send mail if the field is equal to "No" - and when that is the case set the field value to "Yes".
This currently not possible with Flow. Only list triggers expose custom metadata properties. It is currently on the development team's backlog, however, and should be available in the future. You can vote for this feature here, which may make it a higher priority (pure speculation, I have no evidence/proof this will do anything now that it is a planned ...
You can use the Data Management Gateway to connect Flow/PowerApps/PowerBI to on-prem resources.
Flow and PowerApps won't be able to access all data types in SharePoint pre-2019 on-prem, however. Test your specific scenario to see if it works.
You need to configure the onprem gateway and you should have the global admin account to create flow and configure gateway.
Access to download and install the On-Premises data gateway on a
Access to a SharePoint 2013 or 2016 environment.
Already have a subscription set up with PowerApps and Flow.
SharePoint Gateway: PowerApps and Flow
You can use "Edited" trigger, but check document status using "Send an HTTP request to SharePoint" action.
You can use below REST query to get the document with status
Edit the flow, create trigger Recurrence:
Interval: 1 - Frequency: Day
TimeZone - Set correct TimeZone
Start time: Set Time from which it will be recurred like Tomorrows 12:00: 2019-02-16T12:00:00Z
After this Trigger you will have your code with sending an email.
Hope it helps!
Yes SharePoint Online sites can be opened using SharePoint Designer 2013.
You can download the SharePoint Designer 2013 from here
Yes, it is possible to create workflows in SharePoint designer for SP Online sites.
Difficult to tell which approach is the best, but MSFlow are to stay here and the extended support to SP Designer 2013 is going to be till ...
One of the actions is sharepoint: update list item. It will ask for the id of the list item, just use the id of the item from a previous step.
Be careful though, this action is a PITA: if your list has 20 fields, all 20 fields will be added in the designer. choice fields will have their default values set, so you'll need to go through and clear those as to ...
wjervis has the right answer. But to add a bit, you can actually use a "when a new item is created" with a document library, and then you'll have access to all metadata. If you try this, just type in the library display name in the "list name" field. (libraries don't show up on the list, but again, this will work if you manually type it in). But, don't get ...
This can be done with SPD2013 but it is far, far easier with Flow.
There is not a REST interface for SPD2013 workflows, so you would need to do it with JSOM, which makes it impractical if your desire is to include "Approve" and "Reject" buttons in an e-mail.
Flow does this very well, as mohd said:
See Also: Request manager approval for leave requests
I've found that Modern SharePoint Events Lists don't work intuitively with Flow, but with HTTP Requests it is still possible.
When Flow creates an SP.Data.EventsListItem, it doesn't provide a value for the property fAllDayEvent. This seemed to prevent the Event Item from showing up in Modern SharePoint event pages and event webparts. You can view all the ...
Microsoft Flow is a cloud service. You can use it against SharePoint 2016 however you must deploy the Data Management Gateway and use that gateway when making connections from Flow.
There are limitations when using the Data Management Gateway with SharePoint 2016; namely (last I tried) it could not resolve MMS fields.
SharePoint 2010 Workflows may be a ...
If that field is not available via the gateway, change the email to be html, and include a link to the item:
<a href='https://sharepointserver/sites/site/lists/somelist/DispForm.aspx?ID=999'>link to item</a>
In place of the "999", use the flow interface to insert the item id field.
This is now possible, though the action is in preview. The action is "export email", and is an action, not a trigger. So first have a trigger based on receiving an email, then "export email", then a sharepoint create file action, which can use the "body" property of the export action for the file content. (the body property is the email, not just the body of ...
As long as you have clear understanding on what DAY means, below solution can be applied. If your users are geographically distributed around world, it can get tricky, so please take with pinch of salt.
Write schedule based Flow - https://docs.microsoft.com/en-us/flow/run-scheduled-tasks
This flow can Update item to a config list every night say 1AM
use this flow i created few days ago, but in one thing, change to function:
after some chat here is solution with dictionary for upper case words:
Create Custom List in SPO, only with Title. Fill Title with words you want to keep uppercase:
Initialize another variable UpperCaseCol at the start of the Flow which I referred here:
Get items from ...
This is by design. Flows are stored as part of the user who created them, and by default they run under the credentials of the user as well. First, I would immediately contact your SharePoint admins and verify that the Flow has been shared with another user and get ownership transferred, as the flow itself could get deleted.
Because of the issue you raised,...
You can update the Author (Created By) or another field by using REST API _api/web/lists/GetByTitle('<list>')/items(<item id>) and send POST request in the flow.
By default, the Author is read-only field. You need to change the attribute ReadOnlyField to false for this field. You can post to: /_api/web/lists/getByTitle('<...