You can find the release notes at this link: https://docs.microsoft.com/en-us/business-applications-release-notes/april19/
Adding a Map control to your PowerApp can be very helpful to end users, but it is not available out of the box (unless we continue to keep voting here). There are many use cases, such as displaying a map based upon an Accounts address, or displaying the location of a Work Order.
I’m going to keep this introduction short and sweet. If you are making the decision between Dynamics 365 and another software or are wondering how to leverage Dynamics 365 and the other Microsoft productivity tools, it is a no-brainer to use the integration between Office 365 and Dynamics 365. Here’s why:
There are many factors to consider when deciding on a PowerApps solution and this blog is designed to help you understand the costs associated with it. Microsoft's pricing page paints a feature-rich picture, but does not explain much about the costs associated with a PowerApps solution. I have broken it down into 3 basic components that drive cost: Licensing, Onboarding & Training, and Building.
There has been a lot of buzz about PowerApps lately, some of which has involved a new type of app available for creation called a Model-Driven App. This post will explain the benefits and differences between canvas-based and model-driven apps.
This is a common problem with PowerApps that isn’t immediately evident to someone who may be a citizen developer. You want to create an app to view or edit the data you have stored in SharePoint, Dynamics or some other connection that you have made. But why do the Lookup columns or fields display the GUID?
With Microsoft Office 365 and PowerApps, there is no longer a reason to make your employees fill out a paper, PDF, or email template form.
There are 3 main reasons you should use PowerApps for your employees to fill out forms: