April 2019 Release launches with new features for Microsoft Flow
Microsoft Flow’s April 2019 Release offers better integration, new AI-enabled experiences and more to enhance productivity across business applications.
IT Professionals
Refine Results
Product
Topic
Publish date
-
-
Delegation enhancements for lookups, Today/Now, and AddColumns
I’m happy to announce we’ve made another batch of delegation enhancements for Canvas apps. -
Increase your canvas space by closing the tree view
As PowerApps grew to have more features, the amount of space in the interface needed for those tools, views, properties and more also exploded. -
Embedded canvas apps can now Navigate, Refresh and Save the host form
Embedded canvas apps now provide the ability to perform actions to navigate, refresh and save the host form. -
The smallest feature
This has to be one of the smallest features ever shipped. -
“Mayor of the Internet” Alexis Ohanian to keynote Microsoft Business Applications Summit
We’re so excited to announce Alexis Ohanian as our special guest keynote speaker for Microsoft Business Applications Summit, coming to Atlanta, Georgia June 10 – 11, 2019. -
Use new screen properties for responsive canvas apps
If you’ve started building responsive canvas apps by crafting size and position formulas on your controls, we’ve added some properties that may help you simplify your responsive formulas for some common situations. -
Canvas debugging with Results View
Lots of debuggers allow you to see the value of an expression simply by selecting it in the source. -
Nine new connectors in April and improved visibility into trigger failures
You can now see problems with triggers on the flow properties page — making it easy to find out why your flow isn’t triggering. -
Effortlessly find and switch between icons in canvas apps
There is an icon in almost every app or website. A plus icon, a search icon, there’s even refresh icons on your browser you’re reading this blog in right now. -
More small steps…
A quick note on two bite size features. Have you ever wondered why the Navigate function requires the second argument? For example: Navigate( Screen2, None ) Why not just default the second argument? Transitions can make for a more engaging user experience but most folks don’t use them.