I'm once again trying Flow since previously it, as per usual Microsoft methods, didnt do what I want. We can connect to all these other rediculous locations that some may use but all I want to do is:
Create a flow to save an email or an email with its attachment to a SharePoint library. Period. That's it, nothing more fanciful than that. I dont want it to do it when it arrives here or there, or by some sender. As per normal everyday life, the human needs to decide when to do it. In other words I WILL DECIDE WHEN TO SAVE IT!!
So I see when an email is flagged condition, great I'll check it out. (????) Zippo. So when an email is flagged? Flagged as what?? What about when its categorized? Oh ya that's not there, why would that be important?
Well there's "represents a wrapper for batch trigger response". What the heck is that supposed to mean?? Wrappers go on gum.
I guess I'll need to forget to use Flow and use a useful tool like OnePlaceMail for Outlook or Colligo. At least they're untuitive and I can choose when to send them.
And lastly, no, I'm not filling out s form on the ideas page. That's been done by others already and really, this shouldve been one of the first off the drawing board by Microsoft. But please do send me a survey oasking me if I would recommend this to my friends and family. Please.
Well, created a flow to create an item in SharePoint and then email that it was done.
Went into Flow, For my trigger chose, Outlook 365, chose "When an email is flagged". Incidentally, the "?" see more on the flow advises:
So if I understand this correctly, if I am in triggers and see When an email is flagged, that actually means the operation triggers flow when an email is flagged? Wow does that ever clear up things!!!!!
Ok so we go with that, setup the create item, send an email, go back to Outlook, move an email into my desired folder, flag it as "completed", goto my flow, F5 to refresh and...................................................................wait for it.........................................zippo, zilch, nada.
No really??? I would never have expected that. C'mon folks.
Sorry, if in 2018 we're still having these amatuerish issues and incomplete capabilities there's something drastically wrong.
Ya "Flow" alright. Maybe an antonym might serve better: "Lack"
Do you want to save the email which is flagged into your SharePoint library manually?
Thanks for your feedback, I am afraid that there is no way to trigger a save of the email to SharePoint library manually when an email is flagged currently. If you would like this feature to be added in Microsoft Flow, please submit an idea to Flow Ideas Forum:
I would also post this idea to my product team, if this feature is added in Microsoft Flow, I would reply you here.
I have to say - this is a somewhat obtuse response on behalf of Microsoft.
It's fairly clear what is being requested (and pretty much identical to what I need too):-
A means of triggering the automatic saving of certain emails to sharepoint.
When you say in reply that "there is no way to trigger a save of the email to SharePoint library manually when an email is flagged currently" this is not the whole truth.
Putting the Trigger to one side, everything else is there in Flow already - the Sharepoint COnnector "Create Item" (and possibly also the Sharepoint Connector "Update Item" - because I seem recall that "Create Item" is missing half of the functionality most people need at first instance).
It's the Trigger that is the problem.
What triggers the trigger called "When an email is flagged"?
How is that trigger to be used?
What must the user do in Outlook that will prompt that trigger to fire?
If there was a bit more documentation about how this operates, the answer might become apparent.
(What I'd really like to see is a trigger called "When an email in a shared mailbox is categorised "X"", but that's a million miles up the Microsoft fantasy wishlist for me)
Wow look at all the help we've received..............not!
A year later and still nothing on this.
To be facetious and describe this using sexy, B.S. project language: Maybe Microsoft is on a new "Sprint"? We need to be more "agile" so we can "leverage" our "connected resources" around the apparent "program creep".
Thank GOD Microsoft doesnt sell cars. Can you imagine? What you want a steering whell too? Can you provide a screenshot of what a steeering wheel looks like? 12 months later, still no resolution and we receive:
"Is there anything else we can help you with today?" because the current issue was soooooooo well taken care of.