Power Community

Power Community

Sample author name

Lets Create a Productivity Portal for Finance and Operations

You may be familiar with creating a customer self service portal using CRM data but how can you create portals to Finance & Operations with Power Pages? What are the Infrastructure Requirements and Licence Considerations? This session will take you step by step on how to create a productivity portal for Finance and Operations using [...]

Tips for Automating Processes with Power Automate

A demo of streamlining help desk used in financial services using Power Automate and Teams Planner provided simplified workflows and provided transparency into the inner workings of various support processes. We are going to discuss a recent implementation for a financial services client.

Secure your Azure API program!

Within an organization, you typically have a variety of APIs, that are using different standards and security mechanisms. As a result, it is difficult to control who has access to which APIs and API consumers are struggling with the different security handshakes. In this demo-packed session, Toon will explain how you can leverage Azure API [...]

Event Execution Pipeline Considerations for Dataverse Development

The Dataverse provides a .net development framework and events execution message pipeline allowing to overcome the limitations of certain low code operations to achieve user data requirements. In This session we will review the scenarios when .net plugin development may be required to correctly leverage the various event execution pipelines alongside Pre and Post Image [...]

Dataverse Architecture Masterclass

Dataverse Architecture Masterclass - Considerations when developing enterprise scale business applications with the Dataverse!

Power Platform & FinTech Businesses

Have you ever thought about how the Power Platform can boost your processes? You can use Power Platform and other Microsoft 365 & Dynamics 365 solutions to automate many standard processes with low-code/no-code. With No-Code (and usually also with Low-code), anyone can quickly design robust solutions by dragging and dropping visual blocks of existing code. [...]

Create a solution using Power Platform within Microsoft Teams using Microsoft PowerApps and Microsoft Power Automate.

This session will be focused on how an end user can leverage Microsoft Power Platform capabilities within Microsoft Teams and create an end to end solution using the same.

Dynamics 365 Vs PowerApps Solution Architecture and Licencing Considerations

As PowerApps moves into the space of traditional Dynamics 365 Business Application scenarios it has been difficult for organisations to truly understand whether they need Dynamics 365 or if PowerApps is sufficient. In this session I will explain the Architecture of Dynamics 365 and Power Platform Solutions also addressing feature gaps and licencing considerations to [...]

Dynamics 365 Solution Architecture Best Practices

In this session I will discuss all the new features in D365 Field Service that are part of 2021 RW 1

Power Apps Development Best Practices

In this session, we will take a sneak peek at a few of the cool features released in 2021 release wave 1 plan

Power Virtual Agents Deep Dive

In this session I will demonstrate a real world example by creating Virtual Agent from scratch and deploying in MS Teams.

Crash Course in JSON, Odata and FetchXML to Succeed with Power Automate Development

Crash Course in JSON, Odata and FetchXML to Succeed with Power Automate Development

Reducing .Net Plugin Development with Power Automate

For the past 15 Years iv been responsible for .Net Development required for Dynamics 365 Enterprise projects. In this session I will show you how we can now replace most of your .net plugins and workflow activities using power automate for performing customised operations over complex data relationships, cloning records for Sales Process Automations and [...]
 

Sample post title 0

Sample post no 0 excerpt.

Sample post title 1

Sample post no 1 excerpt.

Sample post title 2

Sample post no 2 excerpt.

Sample post title 3

Sample post no 3 excerpt.

Sample post title 4

Sample post no 4 excerpt.

Sample post title 5

Sample post no 5 excerpt.

Sample post title 6

Sample post no 6 excerpt.

Sample post title 7

Sample post no 7 excerpt.

Sample post title 8

Sample post no 8 excerpt.

Sample post title 9

Sample post no 9 excerpt.

About Me

Sample author description
37 POSTS
0 COMMENTS
- Advertisement -spot_img

Latest News

Power Fx: Error handling graduates to preview

We are thrilled to announce that the long-time experimental feature Formula-level error handling has moved forward to preview. As a result, you and your end users will enjoy higher reliability and more transparency about what is happening in your apps. It’s a huge step. Adding error handling to an existing language turned out to be a very tall order, touching almost everything, from data types, to functions, to the runtime. Thank you for all of your support, feedback, and patience as we got this done. What does it mean for you? Your apps will more reliably detect and report errors.You can write blank/null values to a database.You can detect and replace errors with the IsError, IsErrorOrBlank, and IfError functions.You can control error reporting and logging at a central location with App.OnError.You can create and throw your own custom errors with the Error function. Error handling is a big change in behavior. By entering preview, we are signaling that we believe we are done, that we anticipate no further significant changes from here. Many of you already use error handling in production and this move to preview should only embolden more of you to do so. If significant changes are needed from here, we will treat them as a separate feature. We are rolling this out slowly as it is such a big change. All of you will soon see that the Formula-level error handling switch has moved from experimental to preview in the settings (as of version 3.22082). It will still be default to off for most tenants. Over the coming weeks we will slowly change the default for new apps only to on across the tenants. Makers can still disable this feature and will be able to do so for a long time. I say again: we are changing the default for new apps only. Existing apps will continue running as they always have. We have no plans at this time to turn this on for existing apps, and as this is such a big change, we may never do this and make this a permanently available switch. Your feedback will guide us. The documentation for Error, IfError, IsError, IsErrorOrBlank functions and the App.OnError property covers these changes. IfError and IsError are very similar to their Excel counterparts. We are also working on overview docs that will be released shortly. But before that, let’s take a brief tour. Let’s start with what Excel does, the inspiration for Power Fx. For an error like division by zero, Excel is very clear that something has gone wrong with a # error message that shows right in the cell. This error will propagate to other cell formulas if A1 is used in a formula: Today, without error handling, Power Apps won’t report anything in this scenario, instead treating the division by zero error as a blank value. That’s not good, as the maker and the end user of the app have no idea something may have gone wrong: Errors happen. Unexpected data flows in, networks go down, storage fills up, to name just a few situations that an app may encounter in the real world. Makers don’t often think through all the ways that things can go sideways which makes default error handling even more important. Returning a blank for an error is also a problem because blank is a legitimate value in our type system and in many databases. Without error handling, Power Apps won’t allow you to write a blank to a database instead thinking it is an error. So, instead of returning an easy to ignore or misinterpret blank value, with error handling turned on we now report an error to the end user (the error banner) and show the formula as having an error to the maker (the red filled in circle on the control): Further, if you look at the value of the formula, it is not a blank but an error value. Just as any formula can result in a blank, now any formula can also result in an error: Now, we still aren’t showing an error in the label control itself as Excel does. We couldn’t do this generically because, unlike Excel, the error could be on a property of a control for which there is no way to display the error. For example, where should an error on a slider control? Where should an error be shown for an imperative operation in the middle of a button’s OnSelect formula? We settled on showing the end user banner and flagging the control in the design experience. That’s not to say you can’t detect and display an error in that label control. Error handling provides a wealth of mechanisms to control how errors are handled and reported. For example in this case, we can wrap the division by zero with an IfError function to return a custom message in the label: The Text function call is required for type compatibility. Or we can use IfError to throw a different, more specific error with the Error function: Or we can have a catchall for all errors in the app with App.OnError. For example, we can log the error and present a different message to the end user: If we look at the log, we see the details of the captured error from FirstError (and there is also an AllErrors), including where it happened and when it was detected: The possibilities are endless! You now have all the tools you need to detect, replace, report, and log errors, including a good default behavior if you never take advantage of these tools. And, bonus, you can also now write blank (or null) values to databases. Please let us know what you think in the Power Apps community forum. There is a dedicated and active space for error handling discussions at Error Handling – Power Platform Community (microsoft.com).
- Advertisement -spot_img