In most cases, customizers/administrators leave the Date & Time field as Local without paying much attention to detail.
With involvement of time, there are 2 behaviors while creating the field (or changing them, but there’s a catch)
You can change from Local to Time-Zone Independent any time, but can’t change from Time-Zone Independent to User Local once saved this way.
The Date & Time displayed in this field will be converted to the time-zone you are situated in.
Let’s say, the Date & Time is stored in UTC behind the scenes was 25th June 2019 6.30 PM, so whatever was stored, it will be converted to your System User’s local time according to the Settings. See below –
This type of Date & Time of field, the time is stored in UTC, regardless of where you are located in the world.
If it is 6.30 PM on 25th June in UTC, it will be 12 AM in India on 26th June
It’s pretty basic, but needs to be done carefully!
One of the easiest and useful feature of a Business Process Flow is being able to Implement and Action right from a Business Process Flow just with a click of a button.
Here’s how you do it.
Let’s say you have an Action that you want to trigger that the Account was Approved for some sort and you want to alert the Stakeholders. You can have this functionality in your Action and call the Action from the BPF itself.
Let’s say your Action has some logic as below which you want to execute when you trigger Action on BPF
Make sure your Action is marked as below for it to be enabled for adding in a BPF
Once this is set, let’s move to the BPF part.
Business Process Flow
In a BPF, since you have enabled your Action to be added to BPF, you’ll be able to add it as below.
In the Properties, look for your Action Process and select it and click Apply.
Make sure you’ve clicked on Apply.
Now, you’re all set. Let’s see how it works.
Now, this is how you’ll see your Action on the BPF on the record,
When you click on Execute, it will mention (if you don’t have any Input parameters) that there are not parameters and ask for Confirmation
Once you confirm, this is how it will show while executing –
Typically, when you track Email/Appoint records from Outlook, unknown senders are created as Contacts in Dynamics 365?
A new Email from unknown recipient.
And if you track this Email using D365 App For Outlook, a new Contact is created in D365 without you being notified about it.
And the Email from the Saved Contact in D365 appears like this
Now, this could be unwanted. And there’s a simple way to turn this off!
Disable Contact/Lead creation
This setting is controlled from your Personal Settings. Under Email tab, look for the option that let’s you create Contacts/Leads for tracked Unknown Recipients.
Once you un-check the same, when you track the Email/Appointment with unknown recipients, new Contacts will not be created.
And you could identify this by simply going into Emails and seeing that the Email address appears rather than a Contact.
Remember, there are a lot of considerations for security and synchronization. The above setup is recommended for all first time Outlook and Dynamics users. While all this, I would like to summarize the steps for all you first time users!
Here’s a crash course guide to setting up D365 App For Outlook for new on-boarders.
Part 1 – Outlook License
So, you can have any of these licenses which has Outlook service included. Be it Enterprise E3, E5 etc. Basically, you need an Exchange Online mailbox. Also make sure the license is assigned to the user and Mailbox is created as below.
Part 2 – Enable Server Side Synchronization
Once Mailbox is setup for the User. Now, let’s go the D365 For enabling Server Side Synchronization on the user’s mailbox. Remember, you must be a Global Administrator to Approve the Mailboxes.
Go to Settings >Email Configuration > Mailboxes. Open Mailbox you want to enable SSS for.
Then, click on Approve.
Then, click Test & Enable Mailbox from the ribbon.
This is important, if you have multiple instances like Production, Sandboxes etc. Choose if you want to only enable it for the current organization and not else where, select the checkbox.
The Mailbox in D365 will complete testing in a few minutes and you should see the status of the same as Success if everything went well.
Part 3- Enable D365 App For Outlook
Now, once Server Side Synchronization is enabled, you’ll need to go to Dynamics 365 App For Outlook in Settings.
One of the most common requirements is to upload images to SharePoint using PowerApps. From my learning from various sources, I’ll try to “demystify” my explanation to send/upload an image to SharePoint Document Library using Flows on my Canvas PowerApp.
Assuming you have the following things already in place in PowerApps as well as in SharePoint
PowerApps’ Camera/Image control and a Submit button. In my case, the image above is a camera so that I capture the image I want and the image below is the Image control to show me what I clicked.
A SharePoint Document Library to record, say, Incidents.
We will get to the Submit button on the PowerApp once we create our Flow.
Let’s create a Flow to pick the Image from your PowerApp, convert it to binary and send it to the SharePoint Document Folder location called Incidents.
Since we want to trigger the Flow from the PowerApps itself, we will select the trigger of the Flow as ‘From PowerApps’ and hit Create
Once your Flow is ready, leave the first step of PowerApps because that’s the trigger. Add Step to create a SharePoint file and fill in the details of the Document Library you have created.
Fill in the FileContent as above. You’ll need this to be converted in the intermediate step after this.
Now, you’ll need to add an additional step in between PowerApps and the Create SP File step as below. It will be a Compose action.
In Compose action, under Expression, select dataUriToBinary expression and make sure you open the bracket as well.
Now, go back to the Dynamic Content section and select the CreateFile_FileContent to complete the formula.
Click OK on the screenshot above and the formula should be set.
Now, replace the File Content section to take in the Output of the Compose step.
Save your Flow and your complete Flow should look like this.
I’m naming my Flow as ‘IncidentFlow’ so that I can identify it.
Adding the Flow to Submit button
Going back to the PowerApp, let’s Run this Flow on the selection of the Submit button and pass the image.
Now, select the Submit button, and on the Formula bar, add the Flow you created, I named it IncidentRun. Select the same so that the Formula comes as IncidentRun.Run( for you to pass on the image.
Now, pass the latest image on the collection i.e. the same image which is being displayed in the image control below.
Running the App
I just ran the app on the desktop itself, you could do it from your phone too!
So I clicked on the Camera when I was ready, the image appeared in the image control and I that was what I wanted to upload. So I clicked on Submit button.
The flow was successful
And my image was in SharePoint too!
I know it is a lengthy post but I tried to summarize as much as possible. Make sure you have a way to uniquely name each file or else, the same file will be overridden.