Power Community

Power Community

Introduction to Power Virtual Agents

This session is presented by the Microsoft MVP Dion taylor, originally from the Netherlands, based in the US. She works for RSM in their TMC technology management consulting practice as a director. You may want to take a look at similar content by following her on LinkedIn and Twitter as well as he blog. She posts videos every week.

The session is going to be an introduction to Power Virtual Agents we’re will be covering a little bit about how can you set up a very quick 30-day trial and which is so recommended to be doing so that you can play around with it a little bit get to understand how it works and all the different components

Later, Dion will be talking about the topics and the Trigger Phrases, what are those things and how do they work together, The authoring canvas and also presenting up to 4 demos. Then there will be Entities and then more demos.

Power Virtual Agent is Microsoft’s version of a chatbot. The big difference here is that Power Virtual Agent allows users to create these bots using very simple and an easy to use interface really without the need of code. You could still put code in there but you don’t have to and that’s really a big difference with Microsoft’s version of that.

So also keep in mind that Microsoft designed Power Virtual Agents really with three key personas in mind right so one is going to be:

Your Internal Customers, and these could be internal like employees, think about an HR you could have an HR bot that you put on sharepoint and Internal Customers can then write ask questions to the bot without having to call your HR department it could be external customers obviously as well right think about going to a website and asking about the status of your order.

The second part of this is the Subject Matter experts, and these are just the people that really don’t know a lot about coding probably nothing but they do have they are experts in regards to what should the bot talk about, what are some of the topics should be discussed or allow people to talk about with this bot so that’s kind of what that subject matter expert is.

And then lastly we have the ability for the admin and development in case we do want to add some code. But again, it’s not required and that’s what makes this so exciting.

The post AI and Chatbots Saturday – Introduction to Power Virtual Agents appeared first on POWERTHON.

- Advertisement -spot_img
- Advertisement -spot_img
- Advertisement - Advertisement

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).

More Articles Like This

- Advertisement -spot_img