Handling recursive events is an age old problem which can affect any application, moreover it seems to affect SharePoint centric solutions often due to the common need to capture an update event to execute relevant business rules before re-updating the item… which of course is the start of a recursive event (or infinite loop!).
This article outlines a simple approach for preventing recursive events in SharePoint when applying item updates via Flow.
This post shows how to use the Muhimbi REST API and the Microsoft Flow HTTP action which will help you Merge all documents within a SharePoint Online document library to a single PDF. If the document is not already in PDF Format it will convert the file as part of the merging process.
Nowadays people rely on mobile devices and alerts to track the work they need to do. In this example, we are leveraging the use of MS Flow to send reports directly in a format that people use the more: emails. We are using Azure Boards as our source of information for the email. Although users can go to Azure Boards and look at different dashboards, we are bringing the information to them daily using an email.
Have you ever looked for the functionality to add attachments to your Planner tasks when triggered by an Outlook email. This "How To" blog builds a Flow that creates Planner tasks, it then captures the email body and saves it to the task description, assigns those in the "to" field to the task and then saves the files attached within the email to the task.
The Flow in this article will show you how you can use Page Approval Flow in SharePoint Online to create an approval process to post news items on your intranet and extend them to all the other communication locations your company uses including Email, Yammer, and Teams.
Would you like to add e-mails as tasks so that you can follow-up in am an organized manner?
Did you know that you could setup a Flow in 10-15 minutes that will take your flagged e-mails and assign them as tasks in To-do . To take it a step further, you can also assign due dates based on the importance level of the e-mail.
We've been helping lots of folk recently to build Flow's which extract SharePoint list item attachments and perform some form of processing, typically to convert to a single PDF document and share with a third party, or add to a records repository.
The following tutorial is built around a very simple scenario but should serve as a good guide for:
How to extract ‘X’ number of SharePoint list item attachments and process
How to use Flow variables to iteratively build a JSON array
How to merge 'X' number of documents (any format) into a single PDF document
How to dynamically create a HTML fragment and insert into a PDF document
TxtSynchas recently released a Flow connectorto its global SMS services. Our aim is to provide you with the tools so that you can easily make SMS part of your business workflows. SMS is a customer’s preferred communication method. When used correctly, it’s a powerful way to improve your customer services communications by sending short, personalised and relevant notifications. Keeping your customers up to date no matter where they are! SMS boasts a 98% open rate so you can be sure your important messages will be read.
Once in a while, there are situations where the OOTB features of Dynamics 365's first-party apps simply run out. While Field Service can be a powerful tool to create additional value in a service/maintenance business, it also has its limits. I have previously written about Time Entries in Field Service by using Flow and PSA so let's continue on that path and see how we can enable field technicians to sell more by leveraging the power of the Power Platform.
The qualification or disqualification of a Lead in Dynamics 365 is a human-triggered event that kicks off a predefined process. That process will convert the Lead to a new Contact and Account record and also create an Opportunity that is associated with the Contact and Account. There will also be a link back to the originating lead in the Opportunity record. Here is what I have come up with as one approach to copy the Notes and attachments to the Opportunity record automatically. You could also approach it differently by changing the regarding on the Notes from the Lead record to the new Opportunity record. Modify it to fit the way your company wants it to work.
My name is Jay Goodison, one of the co-founders of Encodian and this post covers our recently released 'Encodian' connector which provides a new set of robust actions for creating, watermarking, securing, OCR'ing and merging PDF documents as well as image clean-up operations, bringing auto-rotate, de-skew and de-speckle capabilities (plus lots more!) to Flow.
Can Microsoft Flow replace the Dialog function in Dynamics 365? It is certainly one option. I will show you how to take an existing Button Flow you created, edit it to prompt you for input, and run it from within Dynamics 365.
Time and Expense Entries and their approvals are an important part of Dynamics 365 Project Service Automation. As the approval process in PSA is based on a single approver, we will leverage Flow to build more tiers for Time Entry approvals.
This blog post will introduce you to an idea that allows you to pull products from Opportunity Lines in D365 CE to your Field Service Work Order Services and Work Order Products with Flow. No code is needed to accomplish this!
Wouldn’t it be great if you could trigger a Microsoft Flow from within Microsoft Dynamics 365 CE?
I will show you a Flow that a user can run from within Dynamics 365.
The business scenario is that you want to be able to send a broadcast Text Messages (SMS) to Contacts on a Marketing List. We will use the 3rd party service Twilio and other existing standard connectors to execute this process.
This blog post focuses on extending Dynamics 365 for Field Service by using Flow and Project Service Automation. One frequent business requirement in FS implementations is Time Entries. While that functionality isn't included in FS, we can use Flow and PSA to extend FS to leverage Time Entries.
How do you take that document that a user sent you, get it into SharePoint or Teams with the proper metadata/properties?
The answer is this quick and easy Flow, which will allow you categorize and move attachments into Document Libraries and add identifying metadata as part of the process. Using the sweep rules in an email inbox, you can manage and sort the emails and attachments in one simple process, and also use sweep rules to clean up the emails as they get stale if you so desire. By using Sweep Rules in combination with folders in Outlook and Document Libraries in SharePoint or (/Office365 Groups or Microsoft Teams), you can be very specific as to how attachments can be sorted and labeled as part of this process.
Getting into planner for managing the work of your teams, but you are lost in the total overview! Centralize the planning of your teams by creating them in an automated way toward a plan that will contain all teams.
The only solution to date has been to write a plugin to update Child records when the Parent record is updated. Microsoft Flow comes to the rescue! Using the Common Data Service triggers and actions with a little bit of geeky expression writing thrown in, it now can be done and updated easily.
Flow triggers for a list are understandably limited due to the nature of column metadata, but there are tools that are already part of the inherent SharePoint list structure- the old trusty, reliable List Alert. Used in conjuction with Outlook inbox sweep rules, you can get very specific about how list metadata will trigger your Flow!