A very common type of integration that we are asked to create for Dynamics 365 Finance and Operations is an outbound file integration. You might send a customer or vendor list to a third party system. Or you might send a transaction file to another system.
Here's a pretty neat trick that you can use to send the flow down a different path when an individual flow step fails.
When creating power apps for Dynamics 365 many times it is necessary to filter down to a specific company. The entities that are used from Dynamics 365 contain data for all companies. To give the user a consistent experience you should filter the data with the company
Recently I was working on a canvas app solution, and part of that solution was being able to create a sales order in Dynamics 365 Finance and Operations. If you think about it this is an important skill when creating power app solutions for Dynamics 365. Inevitably you will be trying to invoice someone for something you are doing.
In last week's video we talked about creating a pop up dialog box in a power apps canvas app. This week we will take a look at a little bit simpler solution. There is a function called notify that we can use to send different types of notifications to the user. Take a look at the video below to see how to use the notify function.
When creating power apps canvas apps the app maker needs to make sure to give the app user feed back on their use of the app. For example, if the user enters a wrong value or leaves a field blank they need to receive some sort of feedback on that incorrect action.
Before you start to create an app there is an important step that you should consider taking because inevitably at some point you will want to move your application to another environment. Either a Dev to Test move or a Test to Production move.