scanferro.blogg.se - Creating tasks in outlook 365 from email

#Creating tasks in outlook 365 from email update#
#Creating tasks in outlook 365 from email code#
#Creating tasks in outlook 365 from email plus#

ObjTask.ReminderTime = objTask.DueDate - 0.25Ĭreate a task using a Run a Script rule video tutorial If a reminder time is not set, it will use the default setting for Tasks, usually 8 am on the due date.Īccepted values for ReminderSet are True (on) or False (no reminder) This example creates a reminder for 6 hrs before the due date or 6 pm the day before. To override your default settings for Task reminders (set in Options, Tasks), you can use the ReminderSet and ReminderTime properties. ReminderTime = Date + 2.25 ' remind at 6 AM 2 days from now To use today's date only, not the current time, use Date and decimals to set the due date or reminder time. ObjTask.StartDate = Item.ReceivedTime + 2 If you use a category that is not in your Categories list, the color category field in the view will be colorless as the category is not in the master list. If you prefer to change the Start date, you would add a whole number to the start date line. To calculate the due date, you'll use the DueDate property and add a whole number to the Received date. You can customize the script to set a category or due date (or any other fields supported in Tasks). Set objTask = Application.CreateItem(olTaskItem) Sub ConvertMailtoTask(Item As Outlook.MailItem)

#Creating tasks in outlook 365 from email code#

Paste this code into the VBA editor then create a rule and choose Run a script as the action. For Description, select the plain text content from your dynamic content.Press Alt+F11 to open the VBA editor and expand the tree to find ThisOutlookSession. For the task ID, select ID from your dynamic content.

#Creating tasks in outlook 365 from email update#

Finally, create a new step to update task details.

I added an additional Delay step because Flow was often still creating the Planner task when the last step was trying to update the task description, resulting in an error.

The final step is to send your data to your newly created Planner task.

Next, create a new “HTML to text” step that converts the output of the previous Compose step to plain text.

#Creating tasks in outlook 365 from email plus#

I created a new Compose step, and for the input created the replace function that pulled the email body and replaced closing row tags with a closing row tag plus a line break. In our example, the HTML email was formatted as a table with no paragraphs or line breaks, which resulted in all the text running together. You may not need this step at all, depending on how your data is structured.

This step is where I cleaned and formatted the HTML.

Replace(triggerBody()?,'Marketing & PR Project Request - ','') We wanted to remove the first part of the text to leave just the user-submitted title, so I used a simple replace function: For example, you may want to remove any “Re:” or “Fwd:” In my example, our email alerts had the subject “Marketing & PR Project Request – Example User-submitted Title”. If you need to customize the title, you can use one of the functions. If you just want the email subject line, you can simply select the email subject using the dynamic content selections.

For the next step, choose Create a Task.

In my example, the flow is triggered when a new arrives in Outlook 365 with certain criteria. I’ll also make a couple simple formatting changes using the replace() function and the Compose action. But in our case, the email to plain text conversion needed some additional steps to clean it and make it more user-friendly.īelow is a quick walk-through on how you can create a Planner task with the email body as the task description if there is some complex text cleaning involved. The email body becomes the task description.Īt a high level, it’s a relatively simple flow and there are templates available and documentation on working with Planner and converting HTML emails to plain text. The form then sends an email alert, and the email in Outlook 365 would trigger a flow to create a new Planner task. To make a long story short, new project requests had to come in via a webform on a local server. Earlier this year we started using Microsoft Planner as our project management tool and one of the biggest challenges we had was developing a workflow for project requests to enter Planner.