SharePoint Power Hour: PowerApps Component for Nav

[Music] hello everybody and welcome I'm Laura Rogers and this is SharePoint power our going on a few years now this is a live show Wednesdays at 11:00 central about stuff in SharePoint and office 365 I'm not a dev or an admin this is all just sort of all the topics in between for people that are not super technical but maybe power users and we just go into all kinds of various topics so I the last three weeks or so I started getting in the habit of sending out the newsletter and just putting some things for people to vote on for the topic and we also have this slack channel where we all chat live during the show which is the fun thing about having a live show it's just have a live chat going on where we discuss whatever the topic is and ask questions and today's topic you all voted on was the ability to do a navigation and a power up using power ups components and a couple of the other things I put out there to vote on where Microsoft teams admin and this new thing called access reviews in Azure which I think are perfectly cool other topics but you all voted on this one way over the other one so let me go ahead and share my screen here and talk about this concept so I'll show you an example of what it looks like sort of the end result it's pretty bare-bones and I didn't want to make it super fancy and spend a lot of time just making it giving it a whole bunch of visuals and making it look slick I wanted to really show you the functionality of how to get it to work first and then maybe we'll be able to go in and do a couple of tweaks and you know add some fanciness to it so in my let me go ahead and share my screen here and I took I took an app that I already have and I see and I just kind of crammed this concept into it so it is pretty messy a couple of customer projects that I've done lately I've been doing this you know that as the best practice when I'm creating the navigation just as I'm creating the app but this was a demo app that I had that I'll show you what it looks like and then we'll I'll just go into just a plain blank app and we can build it there and that way you'll be able to see kind of all the pieces parts it will probably take the full hour it might even go over because it's um it's a good bit of just settings and little things here and there to understand it's kind of complicated um so and share my screen and explain what this concept is first so this is my little customers and projects app so this concept is this having navigation that goes across all the screens that you can sort of centrally manage and have it be uniform and also have it be clickable so I clicked on projects clicked on social and have it be clickable to take you across to the different parts of your app and you can stick this component on all the different screens in your app so that's I know it's pretty ugly but there are a couple things going on the first thing is it lights up and shows a different color according to dynamically according to the current screen you're on and it also has the navigation where it clicks and takes you to that page so it's kind of it's got some it knows what you're clicking on and then it's doing an action it's taking you to a page and then it's got some conditional formatting on the this gallery itself that knows what page you're currently on so that it can show you know show a different color so once you know once you understand all those fundamentals then you can start playing around with putting icons in it and putting you know making it look not have this big ugly yellow thing but do maybe your own thing maybe just have the text be bold or look different in some other way when you're on that particular screen so what I'm going to do is let me I'm just going to create a new one take this over here and just do brand new one so that it's because it's ugly when we do a brand new one but it's more simple so it's kind of breaks it down so you don't get overwhelmed with kind of you know anything else going on in there so this is advanced power apps this is not this is not going to be something for if you've never seen power apps before and I'm just creating a new one real quick of course I've got a million tabs going on this was something I was looking at with responsive layouts and canvas apps oh my of course my power-ups brakes right when I get started start over click creates their tests 8:28 all right so what we're gonna do is the first thing that we're gonna do once we spin this up is that we components is still sort of a test feature it hasn't officially rolled out yet so components is not going to automatically be there for us to see in our power I might just have to open an existing just blank power app that I don't know why it's all of a sudden being weird let me see it real quick yeah I've never seen it just asked me to authenticate over and over again but I do have another just blank power app that I can play around with in here I did one when we first when the concept of components first came out I did a Power Hour on just introducing components so I think I did that in my other tenant though I'm sorry I don't know why power apps just you know like I said it's live on the fly but usually power apps is not going to just completely not work and now I have to sign-in gotta love live demos so but I have the power app built that has it all functioning I just thought it might be a little too complicated and just because the settings are so everywhere to try and show you everything in the existing powerup so I was hoping to just create a new blank one this is a different tenant so let me see if I'll let me create a different new blank one over here good grief right oh so you've been dealing with that too okay so there's my new power app so we'll have a few different screens not why I don't know I'm duplicating something doesn't have anything on it but there will have a few different screens and will have a component and we have to turn on the ability to have components so we have to go into the advanced settings and component we have to turn that on so that that has to be turned on for us to be able to see all this different stuff that we're doing in here all right so then when we do that we have this tab called components and what we're going to do is add a new component and we'll call this CMP top of and then in the component we'll add a gallery and I'll just make it the galleries away over here I'll make it a blank horizontal gallery and then no I don't need an existing data source I'll just kind of move it to the top this blank space at the bottom doesn't really affect anything it doesn't really matter so I don't need to make it perfect but whatever size I put it in here that's the size that's going to show up at the top of all those other screens all right so I've got my blank component and then I'm just going to put a label inside it stop asking me to select a data source so I inserted a label in my component and so each one of these is going to be sort of what my navigation text that's going to be where the navigation text is so I can make it bigger or smaller bold that kind of thing and then I need to have what my items are gonna be in my gallery so let me let me name stuff correctly first and now my nav text then my component itself needs to have some input so that's where I get to this sort of some slides that I put together explaining what what these some of these concepts are before I just dive into throwing stuff together and you all and the fun thing about you know having this bit live is that we can chat and have a conversation throughout and you can ask questions and it's very interactive okay so you can see my slide right hopefully okay we have a collection that we're doing when the app starts so in the on start of the app we're doing a collection and these are this is what we want to be in the navigation so then we're collecting or creating a name which is the word we want to show in the navigation for you know the customers the projects whatever it is the screen text is the name of the scream you want it to navigate for say you know customers whatever it is and then the screen is the name in the screen now these this is kind of confusing this is where it's this is the most confusing part about it I initially had tried to have just one screen filled in here and have it be the screen the actual name of the screen and text with quotes around it but it it may it didn't function the way you kind of want it to in it the whole component became really slow and became very cumbersome and it once I kind of split it apart and made it into two different ones it work it functioned a lot better because when we are navigating when we click something that we want it to navigate us and take us to a page that navigate action that we're doing needs to have the actual screen name that's not a tent it's not text it doesn't have quote around it it's just the name of the screen because it needs to be able to associate that with the actual names of screens in the app and take us there it won't take us to something that is just a piece of text right so that is the most confusing part that one of the things I wanted to lay out for you so it's screen text and screen are the exact same thing so like customers SCR customers that's in quotes and then just next one is SCR customers okay the inputs now when we're in the component this is where the next step of what we're about to do in that navigation component I just created and these are the inputs they're going to create some different inputs and outputs for the component with me so far can y'all can y'all verify that you can see my screen your phone you want to make sure you all are very much more quiet today than usual so sometimes I'll just I'm just talking and go along and I don't realize that you know the app crashed or no one sees my screen so there's also a delay to when I talk and when I can see your comments okay so these are the three input the two inputs that I'm putting in my component I have input page and it also lets you put an actual value in these inputs and outputs but this one is empty input page is and I also need to say what type those are too I'll have to add that and an input table as an actual table an input page is just text and an input table as a table and so we get to that screen you'll see those so the table is it's going to be showing that collection that I collect showing all the navigation but that table needs to put itself in the component and what I had initially done and was and it lets you do this there's no way to necessarily know that it's not a best practice or that it's not what you're supposed to do was I had put the collection directly in the gallery inside of the component and turns out that was what was causing my whole app to be slow and by every time I clicked on the components screen to go back and forth it would take like five minutes because you're not supposed to just have a gallery something inside of a component refer to data from your app so that's why I'm passing it in as an actual table parameter into the component and then my outputs are my gal top nav which is my gallery in the component whatever I select the text of whatever thing I'm clicking on so I need to pass that out to the app so this is it's kind of weird because the component is like a completely separate entity so that's the thing about components is the component is not just it doesn't just know about your data and know about the fields in your app or values here and there like everything else in your app you can just refer to each other just anytime you want well components a completely separate entity so anytime you want to get data from anywhere in your app or get information from any other control anywhere yet you have to create these parameters to pass in input and output to tell it exactly what to get from the rest of the app and to send out from the rest of the app all right Stacy said my voice is off from the video that's awesome that usually happens when the when it's like a slow connection or something hmm I can you know what I'm going to do I'm going to try and close a couple of other things that could potentially be slowing it down I don't know close one Drive I don't think it's doing anything but that's really annoying if you all are seeing my my voice all separated from my picture disabling a couple things okay so that makes sense so far it's a it's a very advanced topic alright oops so we've got in the component did I go over the OSA then outputs so our page output is whatever selected then we have this navigate trigger so the first time I demonstrated components to you all and I was introducing you to this concept of components we were trying I had never done anything on components before I'd never use them were just kind of poking around and trying stuff and I could not I could get it to show potentially some navigation but there wasn't any way to make it trigger and do something and do an action when you click something when you click a component component doesn't necessarily it doesn't just have it on select like everything else so the method that we're using to trigger an action to happen to trigger us navigating to another page is that were hat we're putting an extra extra little just a toggle switch on every screen in the app and when a toggle switch has an on change that will actually trigger an action so that's a sort of a little just advanced tip and power apps is that something if you have something that won't trigger an axe and a toggle button on change will trigger it so if you change it via a variable like programmatically that change will trigger whatever action you define in the on change property okay so that's what this navigate trigger is that we're putting as an output and we're putting as a value in here putting this variable nav temp and I just called it temp because it's just temporarily toggling it on and then back off so that it triggers for us to navigate and it's Tritonia back off just in case we go back to the screen and we need to do it again Tereus is kind of recommend power our sharepoint power bi i think it did one didn't I do a Power Girl it's been I mean it's been a while maybe a year but I did I'd have definitely done a power bi Power Hour and I think I ended ssso SSRS ones a long time ago okay in the components this is that component we just created so we're in the little component interface of putting a horizontal gallery in there put a label you saw me do that now another thing we can do which we might do towards the end if we have time is put something cute like a little icon for each thing we're navigating to and then this is the part right here this template field this is the part that's showing it a different color if we are on that screen so that whatever screen we're on like you know I showed you it was yellow it lights up yellow so this is kind of this RGB a is like just sort of a faded white that I'm using so instead of just putting solid white it's like a faded because it's got the point eight so if the component top nav input page equals this basically this screen that I'm on then it shows as yellow otherwise it's white so that's the template fill property on the gallery okay so then when you insert the component on the screen we'll go over these in a second so let's go I'll go back and go into some of these settings so these custom properties these are like parameters that I was telling you about so I'm going to go to my create a new custom property and I'll call it input page and then that's input and then this is important it has to be txt and then I'll do another one that's the input table and that one is input and it is a table see there's a lot of different types of input I did try using for the screen I did try using the screen went in here and when it was on a screen instead of text that's one of the things that made the whole thing really slow so when I got rid of that it actually it made everything much smoother and faster so you you're probably sitting there wondering if you've done this before why I didn't use screen but that just didn't work out I could have potentially been doing something wrong but texts seem to make this thing much faster than trying to pass the actual screen so I've got two input properties and I'll do output and that is and as text and then oops did I make it the wrong tight yeah it's supposed to be output text see it puts a little separate section there and then this one is navigate trigger and that is also output okay now got all my inputs and outputs set up now this is the part that's kind of hidden that's important that to go to also so when I go to the Advanced tab that's where I can set up the defaults for what what what needs to be in these like what information needs to be in these little parameters that I just properties that I just set up like you call them parameters it's kind of what they are so over here we and I put this in the slide I put that this is empty this input page and then for table you don't need all this sample stuff that it's gonna give you by default you can do and this is what I had in the slide I'll go ahead and just go to table up here input table this is going to be the same this is the structure of that of that collection that I'm doing at the beginning of the app on on start all right and then and I haven't I don't think I put that in here yet okay and then the page output is gonna be down now that's my gallery over here got selected dot screen and it's not resolving it yet let me just flip back and then back over and then see if it yeah so it kind of let's see now it still thinks it's that fake this is kind of funky I found that kind of going back and forth and once I set up some of the other stuff in the screens this some of this actually works a little better and when I was doing this I was just kind of going back and forth and setting this multiple time I'll just have to go back to this one all right and the nav triggers gonna be that variable which I haven't created yet so it'll probably not like that either yeah so I haven't created this variable I'll do that one later too because that variable is going to come from the app so it's coming from the app into the component and that will that nav trigger is going to have the value of that variable okay now also so this still has all this fake data in it because I haven't done any collecting yet so for my app I'm going to do my collect so on start and then clear collect now I'm just pasting this from my other app but I want to we want to kind of define what the screens are so these screens I'll give them better names so I'll just say like SCR one just coop super simple SC r2 George they're just to make it different so that you don't think that they have to have numbers on so cut 1 2 and George so this is gonna be I'll just stick something on this page that says screen 1 just so when we navigate around we can tell we can visually see where we are there okay so then we need to have so I've got some nice screens so they're gonna be 1 2 and George and then we're going to oh yes somebody was asking can power house be considered as a replacement for an index forms no not necessarily an intake forms is perfectly viable and active product it's not going anywhere and it is unless you I mean unless you just don't want something that's I don't know it maybe nin text is more expensive than power apps but that's the only there's no reason to drop an in text and go for power apps and in Texas probably got an easier user interface and doesn't have a lot of those crazy complexity with some of the stuff it power-ups has I did a whole I did a wrote a blog post the other day called stop stop using InfoPath and I put link a link to the whole playlist of me comparing all the form products like four years ago and then text was one of them but I was just going through kind of the interface now of course it's changed by now but just the concept of looking at all the different form products that was before power apps even existed so yeah so we'll go read my stop using InfoPath blog post okay um so my screens screen one two and George so I need to go do my on start and make that kind of screen in 1 1 2 notice I've got quotes around one and not quotes around the other okay and now they all kind of now that I finish typing now I'll kind of resolved in our okay so I'll go ahead and oops I'll go ahead and run this might run my own start and so now I can see when I go view my collections I can see I have this collection now of the name the screen and the screens text and then I let's go back to the components let's see if it likes me any better now see page output çal top now it still does that anyway we're gonna worry about that right this second okay we'll just have to come back to that cuz it it does need to resolve what's in there okay so that's my input table oh and then for my items Oh see that's what I didn't do I didn't do the items my items property and I'm going to change this items property you'll see when I get want to you'll see what I'm doing when I start putting the component in all the different places in the in the app so parent input table and then my say what's it doing so instead of the text saying sample heading like it did by default and now I'm going to say name and that's going to be the name that's going to show from the navigation so what color do I want I'm going to make that have at least your color so just to make sure no there's nothing in there right now but I want I don't want that to be white or invisible I want to be able to see it and then I also need to do that template fill the template fill is also something that I showed you in these slides if the component top nav that's this component dot input page is equal to whatever screen you're on that's why it's going to show it yellow otherwise it's going to show it white now let's go back to the screens and then I've got another slide so I'm going to insert the component on the screens and then so I'm also going to insert a toggle control on each screen you can see I kind of threw this together right before we started the tableau control is the part that is going to make it actually navigate and do that action so the input page is going to be a property when I insert my component on all these different screens these are going to be properties all these things that I created as parameters that I created in the component those are all properties that I can set that I can put a value in when I put the component in my app so these are this is what we're defining when we insert the component all these different screens we could just really insert it on one and then copy and paste it to the other ones and then we'll insert a toggle I just like to call it toggle nav trigger and on the chain on change that's where it's going to navigate so we'll put all that together now to okay so I will go so I'm on my screen one and I go to my insert tab and just choose components I've only got one component so I put it on here and I don't see anything in it yet and it automatically for some reason puts it at the bottom so you might want to be aware of that you might if you have a whole bunch of controls on that screen you might want to note to bring it all the way to the front so that you can see it it'll just kind of go like that also let's go to my component and I'll put a fill color on it just the whole thing so that I can see what's going on oh let me just go here and go to my fill there so now I can actually see it so now I can see that too so and we can can talk about the width - so the width of this gallery can be parent dot width so maybe that yeah so that stretches it across okay um do I have what else do I need you know I need to put the other properties over here for what data it's going to show so for my input table this is where I'm not gonna put that little just sort of empty placeholder let me go up here I'm going to put my collection tada look at that okay so lease that's a good way it's an interesting way of putting it a run option for collections we are you saying just to generate the collection or actually to make it trigger and make it do something when you click on something are you talking about what I did with the on start alright let's see okay the input table is that collection and get back over to my component and I need to have an extra toggle now I'm gonna insert a toggle button and we're going to hide it we don't need to see this oops I don't need to put it like right on top of my opponent but this is something that we're gonna have on every screen that we're just gonna hide it's just gonna have a visible is false so I'll call it to trigger oops tgl not to feel okay and then it is going to have where some my settings on this thing the on change and I put this in one of the slides two on changes the main thing that we need to focus on so it's gonna navigate to let's see where does my my component top now one so this part where you're telling it which component to look at now every time I certain I component all these different screens this is actually its own control so the navigate on each different screen needs to be talking to that particular component on that screen so this is CMP top nav underscore one so I'm just gonna make these so they have names that match so I'm just gonna put an underscore one after that one two just for some symmetry there okay and then my defaults for my toggle it's gonna be I have trigger the nav trigger is the thing that we're we're sending it and telling it to go off and on right and then what we can really do is just take this whole toggle and just hide it so just go visible false all right so let's screen one and then I need to go to I need to take this and first I want to see if it works see if I've got everything in place I don't think I have everything in place yet so let me go back to the component I have to go do a couple of these things yeah see the nav trigger is not set up yet so that's not gonna actually do anything so my dad selected dot there it is screen text see I knew it would have I knew it would appear and now that I'm see I'm not defining my variable nav temp anywhere yet am i only see no I don't okay so that's another thing that I need to define because when I click this I want it to toggle it off and then back on oh where did I do that I see I've got to see that thing about this that's so tricky is this just got settings everywhere and that there is a action somewhere that I have where it's turning it off and then back on and my other one and I got to go find it on select yeah I think that's what I did yeah okay over in my component that's right to do the on select so here my component when they click on do I want it just when they click on the word on the label or do I want to make this on select B for just when they click anywhere in this whole each entire item so I think I'll just do the on select just for the whole gallery so as long as this this is just has to do with galleries so as long as this label has its on select as C select parent which is the default every time you put stuff in a gallery then you're you're doing the on select for the just the whole gallery which sounds weird but it really it knows which specific item you're clicking on and it runs on select for that item so when I click on something it's going to set that variable very nav temp to true and then set it to false so that's where that's where it's going to trigger the on change of that little toggle okay huh look it went to screen - OH all done what do you think okay so now I haven't put the component and the toggle on that on the second page yet so I need to copy those so you know your if you're kind of wondering well why would I want to do all this as opposed to just putting a gallery on each screen while we don't want to go to all this trouble well then you have just one central place where you can manage it in one central place where you can make changes to visually the way the gallery works so I know even if you had a separate gallery on each screen you could do the thing with the collection to define what's in the collection in a central place but this one gives you the ability to define what that whole gallery looks like just from a central place by going into the component and doing that like I want to Center those words and I also want to make sure that when I that all these little references [Music] I'm gonna wanna make sure that all these little references are pointing to the right to see this toggle yeah so component top nav underscore 2 nav trigger that's important and yeah so they are pointing to the right component so that's the one to underscore 3 that's why I did the underscore 1 under this toggle just so they would all line up and match up so let's say if I go 1 2 3 so yeah I am now it works I'm navigating between screens but the thing is not lighting up the color is not changing so something's still wrong with that part so I need that let's go look again at the the color of and that was my template fill if the component top nav input page equals this item dot screen text yellow otherwise let's see page Oh input page no I don't need the input page let's see um time to have dot input page I need to be sending at the input page though so let me see and when I go to here oh yeah so my input page is empty input page yes and this is one of those things that exists for all apps this whole active screen thing so anytime you want to know what the current screen is that the person is on in your app this active screen dot and all this information about it dot other things is all available see name background image blah blah blah it's all available to use just anywhere you know formulas okay so now that I've got the input page of whatever screen I'm on sending it to the component now it functions so I do I needed to do that on these other ones too so I could just go and I should have done that on this first one before I copied it and pasted it to the other you know all the other pages but I'll just go just copy this one since it's just one little change I'll go just paste it to the other one so that's the trick is you just get one on one page working right and then you can just copy and paste it to all the other screens and then there's not really anything else you need to go do separately on all the screens okay now let's try it again one two George so now it works now let's try sticking an image in it making a little slicker making it look a little nicer so like this label I can Center that and then put an image so to do an image then I'd have to have images so I can go upload I'll just go to my media go upload some stuff I think I've got some PowerPoint I mean not PowerPoint power apps just little buttons I've created that look kind of nice I'm just gonna pick a few random ones certificate city white and gift okay and I'm just gonna randomly assign these to my to my items in here so I will go to my that's gonna head be part of my collection now so now in my collection I'm going to put the name of the image in here and that was a certificate it actually resolves it which is interesting the city white was the other one gift there we go may go double check yeah okay so then when I do my collection I'm gonna also define what image goes with each of these navigational components what I want to see along with it so let me go ahead and run that so I'll have all that in my app now it's not showing in visually in this navigation yet because I need to go add that to the component so in my gallery I need to go insert just an image control kind of make it a little smaller and move it to the top like that yeah so you have to kind of line these up so that the image doesn't cover the text and stuff like that so then instead of picking a specific image that's where I'm going to tell it to use the image that that's part of the collection so I know that though let me see my label oh it's gonna be this item dot yeah it just doesn't know that I have an image yet because I haven't defined that in in the properties of the right here and the structure of what the table is so I definitely would help if I would have done that is you know when I was first creating this collection so I wouldn't have to go shim it in there later just put empty quotes there all right now what happens now I broke it okay let's see um my component so when I changed that little C when I changed this thing and the component it reset all these so I had my input tables at showing my collection of my top nav but and I put that in this input table property when I first put that in put that component on this screen but then when I went and changed what's in the input table are in the gallery inside of the component then that like reset everything so definitely try nope not like I'm doing and try and think through it all when you're first setting up the component and putting it on all the screens that way you don't have to go back and shimmy stuff in here so input table now why is it my image showing let's see um now put little quotes around the image when I inserted it in there no this is one of those things you know like I always do towards the end of Power Hour is I kind of add something in throw something in then I didn't necessarily plan um so I hadn't tried this one yet this is the the all the other stuff I had all set up I had my slides and everything but they're sticking the image in there is the thing that I did not think through okay let me see if I do if I do certificate oh maybe I need a you know what I need to pass that in because it has no idea remember the components a completely separate thing in my app so it has no idea what images I've put in the media thing now in the media section in my app I have to send it that information so it's just another one of those little inputs and outputs that's one of those yeah I think I might need to run the app start again but it might be because I don't have that in this component doesn't know that let's let's go look let me see run on start again I could have sworn I did that let me go look at my collection so I don't know if I can't see these because I because it's in the collection that you know what a good way of testing that is to just stick a gallery just anywhere in my app so I can just make sure that the collection is working first and then troubleshoot why it's not working inside of the component so galleries way over here not sure why you've got kind of relegated all the way over there and then I will do my yeah so my collection is yeah it's working so it has all the pictures in it so I just stuck a gallery you know just on a random page and it does work so this item died gee that does work still I think I need to pass that information to the component though just like I'm passing all the other ones let me see where it's the fact that this is in quotes I'm not sure so see the name text I'm not really passing like just this text this name here I'm passing the name of the page so that it will show me so it will know to light up the right thing but let me see my input table yeah so I don't really need to have the image in the component yeah I'm not sure I'm not sure whether to try and put it as is it the color of the image well the image is on is white and it is on top of this so it should be showing we can just let me go ahead and change this template fill so it's not so white so it's more faded there [Music] oh wait let me see Oh image there we go that's what I didn't do look at that so in the component the components properties I have to go add that in because it it had just sort of a little blank see this all cut got this all got reset when I reset the whole structure of what my data is then that collection so this got reset from my input table when I had to reset those so let me go change that so image is that name is my name screen text screen text okay woohoo kind of working all right and then we you know you could probably do another let's do one more thing let's do like make it bold or something so with this label right now we have the logic here changing the color I'm just going to take kind of the same logic I'm gonna make this text bold so I'm going to go into my font weight I'm going to say if the input page is equal to this item then I want it to be bold otherwise semi bold and then I'm also gonna make that text white just because it looked a little odd being black text back over to the screens and that yellow definitely looks horrible behind the behind the white no it's not I see I can't even tell if it's semi bolt if it's bold or semi bold cuz it's all it's got that yellow going on but you kind of get the idea right yeah definitely think through it first and build it at like like I mentioned like Craig's kind of reham ffice icing there so that you don't have to try and show me things in later and then stuff stuff breaks so I have one that I did for a customer that's really cool with kind of this concept except it's vertical down the screen on the left and it's what this big long form that they have to fill out so each in this form has got this is the one that I mentioned last week where it's got like you know eight pages and it's not one form control it's a separate form control on each screen that takes them through all the little sections of the form so that's what I did for that is I use this as that it's going down the side and showing them what part of the form they're in and I did write a blog post wonder Laura comm on forms across multiple screens on how to get that to function I also didn't want them to use the this navigation if they hadn't saved the form they were editing so your form control actually has a you can do form name dot and it has a it'll see what's it called Oh is unsaved form name dot unsaved and it's a boolean yes true or false and so if I passed that as a parameter to into my component so I set this this whole thing to be disabled so they couldn't click on it if they hadn't something unsaved on that form so it's just another little fun bonus thing that because I wanted them to actually click the next button which does a you know a submit form because if they just randomly go navigate somewhere else and they just changed something then it wouldn't save their changes so it just disables the navigation any last questions and go back all right that was fun I will probably send out another poll for next week's topic and I we do we're teaching the I'm teaching the September power apps and flow live class it's in about a month it's a September 24 that week it's three days of power ups and two days of flow but you could just sign up for one of them and that's on iw intercom and I did put a link to that in that newsletter that I sent out today alright thanks everybody for coming and for voting have a good

Channel: Laura Rogers

Views: 2,963

Keywords: SharePoint, Office 365, PowerApps

Id: RVN4m2OK4sI

Length: 55min 59sec (3359 seconds)

Published: Wed Aug 28 2019