Send Populated Validated with airSlate SignNow

List required field notification

hello everyone and welcome to this video today we're going to look at forum level validation in perhaps and I know it might sound like a boring topic but truth be told if it's not done correctly it could actually create quite a bad user experience and your users can very easily feel like they're being shot at at both our apps so we've come up with a way that we prefer to use it and we've reviewed it for a while we think it works very well and this we're going to be showing you today truth be told is that for the longest time we've preferred to use patch in order to commit data but with responsive designs we've realized that to manipulate the way that the forms or the fields are being displayed displayed on the power app becomes quite a mission if you don't use the Microsoft form so with a perhaps foam roller so we it forced us to relook at the way that we use these forms and to face our kilise Hill which was the validation other forms or something that we really didn't like in the beginning so we're going to show you the problem before we get into the solution and so thank you for watching and let's get cracking alright so here's a very basic bar app and we're now gonna add some validation to this form at the moment we go and add a new expense it's allowing us to submit this record without specifying all the data and that is a bit of an issue for us so what we want to go and do is mark these chords as being mandatory so let's go click on the title and if you get a required just make sure it's unlocked and then go and set that to true all right so that's fine expense amount unlock it under advanced and then go to required and set this to true and same here for the description expense claims are useless if we don't have descriptions and the same for date created so just going to say quiet is true all right so this works well but power apps is actually putting the little asterisk over here to say that this is mandatory and all of these things work well but if you try and submit this with art these fields being populated you really get a very abrasive error so you get read all over the screen you get red and red notification bar at the top and all of this is not very pleasing to look at so we've had a look at at multiple ways to go and fix this red area at the top so we've tried to going to put this back into the studio so we thought about customizing this errand this error over here but the problem is that you then lose any native errors that you might get back from the data...