[Music] [Applause] [Music] [Music] [Music] hello everybody and welcome to another episode of you and I Builder live the show where one day we're gonna have a tagline my name is Maria Gabriella Cho press wector and today we are joined by a bunch of awesome guests but first let's introduce ourselves starting with the top left corner hey everybody Brad Tilton I am on the outbound product management team for our AG experience products here at service now and I am also on the product management team for our whatever he said agent experience agent experience products all my name is latel I'm a product manager for our next experience framework and developer tooling and component development hey everyone I'm Wolf Gang I'm a software engineer working on the things that that M has talked about all right I like we got we got good patterns going here yeah yes so Brad um I wasn't supposed to be here today so I'm not quite sure what we're doing can you uh give us a quick intro yeah I I give a quick intro so uh wolf and alop are not new to uh this show they were on uh what was it August uh when we released the first version of the NEX experiened developer tools Chrome extension and kind of walked us through how that works and so today they're going to share some of the new stuff that we have in the extension I think probably a little bit of uh CLI talk as well um so the new things that are coming out along with the Washington DC release time frame um so yeah I'll turn it over to you guys awesome thanks Brad thanks Maria for having us and it'll be great to share kind of where we're at with every one and obviously feel free to leave uh feedback inputs thoughts in the comments and uh we'll get started here um so we're gonna as I said we're uh you know really own the ux foundations around uh developing components the next experiences workspaces Etc and so um we're going to start with kind of a high level uh we're going to share some of the highle road map with you folks and um would love just to kind of get some input and ideas from you guys as well right like we're sharing kind of where we're going but we'd love to also validate that and make sure that it's the right things for for you for all of you folks uh as we go forward here and two quick notes first I would like to say that I think it's the debut of us ever having PowerPoint slides on this show I know I think we've done a solid year without that um happy occasion but the next thing I wanted to say is forward statements these statements are intended to be covered by the Safe Harbor Provisions contained in the Fantastic producer making sure that we read Safe Harbor to everybody so the last thing I wanted to say before lb keeps going is that we're going to have links to the next experienc developer tools Chrome extension in the chat and in the description so you can check out the stuff that they're going to be talking about yourself perfect thanks Gabby all right all right so really what we're going to uh I'll cover this and then wolf my partner in crime her is going to do a live demo for you guys and I'll keep my fingers crossed and and hope the demo gods are with us but really uh the next experienced developer tools as uh Brad said officially launched in August really it's it's a great tool to troubleshoot debug uh next experience pages and issues that are happening in them as you're developing them or kind of trying to find out what's going on uh in no we've released twice since that August release and have a bunch of cool features that are coming in in November we added the ability uh if you if you recall in August we created a profiler uh as part of the release and you could check out the performance of your pages well we now have a way for you to also automatically stop recording of those pages when the page is done loading so you don't have to kind of guesstimate we've also added some usability improvements around being able to only view uh rows that have nonzero values when you compare two different performance profiles so you can really just see what's changed and uh just having that same view as part of the events table and in March uh which we just recently recently released and is out there now we have a new homepage with indicators and really what we want to do with that is start to surface some suggestions recommendations or or important metrics where that that can ultimately help you find issues but without having to spend a ton of time debugging and kind of looking at a bunch of different things so we'll have some key uh metrics that you can kind of look at and kind of uh start using as a good way to ensure that there aren't issues with with the pages that are being developed or implemented as well as starting to surface server logs and this will only be available for admins but it'll you'll see some of the server logs that will be available and in the tools so really we're starting to create this tool as your one place to go to for all things needed to debug and troubleshoot client and server side and we'll continue to do that as we go forward here but this is kind of the first step in that direction since you guys are on the Chrome since you guys are a Chrome extension are you also tied to kind of like the store release Cadence or do you have your own kind of release schedule we try to stick with the store release Cadence for the most part where we do the bigger releases about every three months uh we will do you know smaller releases on a monthly basis if we need to for defects or kind of like minor issues that come up but we try to stick with a three typically the three months because that gives us a good window to actually you know get some meaningful development done and in quality and all of those types of things makes sense all right with that I will turn it over to my partner in crime wolf all right uh let's see here I think I should be sharing a window are you getting it yeah awesome cool so allop already showed we're in the Chrome Store I don't really need to go over that part here but when you have the developer tools installed I'm on a Washington instance here I will open up my useful Chrome developer tools here we add two new tabs for inspector and profiler uh inspector I'll start with the stuff we added there which is the home and log stuff um so on the homepage we have a series of cards show up related to data we're collect cting about the page that you're on right now I picked a page that happens to show several different potential issues that are happening on the page um so we have uh we built out more information about the components on the page and we started the initial stuff for actions um so when it comes to components uh you get a count of how many they're on the page and then we look for some potential issues uh with the data with the components that are on that page um and so just as taking an example the first one is we we look at the selectable props which is selectable properties is a feature of the framework that allows you to connect data between different components in the tree and um so in this case we found three of them have issues with the mapping of those properties um and all of these come with you know detailed explanations of what's going on here but just to sort of dig into what you can do with this information if you click on details it'll take you to this um part of the components where you see the uh the three issues that we are talking about with broken selectable props I happen to know where they are on the page so I'm going to show that as you hover over them it shows you where that component is on the page that's having the potential issue and then if you want to you can click into them and then you can dig into the details of the actual properties and sort of figure out what's going on with those very similar with uh some of the other indicators we have around State or the depth of the um the tree of components when that gets particularly deeply nested that can run into some issues with performance and you know all all sorts of other things um I think that's what I had to say about the home U and then each of these becomes uh when you open them a filter that you can clear and just go back to the regular components view I I really liked the homepage that is a nice um because before when you came in you just got this components tree and it was it was kind of a an Abrupt you know yeah all sorts of data now but I don't know where to start yeah yeah this is this is obviously just our first pass at things where're we're going to continue to build and expand on what we've l the groundw work for here and is this out right now or are you showing us something that's I'm I'm using the version that just got published earlier this month that all I've mentioned right now so this is already available and this can be used on earlier so while it's kind of part of the Washington release this is can also be used in scen on previous releases like Vancouver correct there aren't any family release dependencies for this particular functionality yeah the stuff we added is doesn't rely on anything that's newly shipped in the platform it's pre-existing stuff awesome um okay so with that I if there's any wasn't anything else I think I'll move on to logs I have a random question this is probably a dumb question but if I installed this in August is it going to automatically update for me or do I have to go update it if you install it through the Chrome web store um it it will update at least the the Behavior I've seen and chrome obviously Google could change this any time the Behavior I've seen is it will update whenever you completely close and reopen Chrome it won't update while Chrome is running that's the experience I've been getting so far nice and and some of it'll also depend on if if you've manually updated that preference to not have it automatically update then you won't get it but yeah it's it's also possible depending on like your it they could also bypass updates and things like that so the default Behavior if you haven't customize anything is that it'll update when you completely close and reopen Chrome yeah and if you look at extensions I believe it was three was 3.2.1 is that the right version we had wolf is 3.2 something I think it's 322 actually okay we've currently shipped um yes 322 oh I could have looked here as well y all right so let's move on to logs sorry can you just get back to the home real quick at component IDs yeah um so if component IDs if there are component IDs with the same ID uh we will also surface that so hopefully that is another functional Pitfall that you could fall into yeah good news everybody I tested it myself by kicking myself out of the stream but if you completely shut down your Chrome it does update Magic okay ready to move on yep let's do it all right cool so logs um I think I mentioned this um we're the version we're shipping today is going to support uh serers side logging so it's kind of similar to um I don't know if any of folks on here would have used the session debugger before um but we've sort of brought a lot of that same functionality into here um where if you hit the record button here and then let me just say navigate somewhere it's going to do a bunch of things on the server you'll see um logs will start coming in here uh I'm going to dismiss this warning about something that's coming in the future um and so you'll see that like it's a table of the the messages uh when they happen the severity so we have filtering on those um so for instance if you don't want to see the info messages you can see just the warning and errors here um and then let me move this so I have more control here um yeah and then if I put this back I'll have enough that we have pagination on all this sort of stuff uh Navigator around let's see um what else is there to say about the logs all up and we do truncate but if you like look at that second to last if you hover over it you should be able to see the full uh message I think if you want to just show that real quick yeah I'm Hing but yeah so yep um this will however you will you will only be able to see the server side information if you're logged in and have the admin rooll we don't want we want to ensure that this is not visible for anybody you experiencing your page Etc so it is in it is particular that you'll get an authentication error um if you do try to access the logs and you're not logged in with a with a admin roll at minimum um but yeah that's that's kind of the only other Nuance to this that's really cool not something I would have thought about but I'm really glad that you guys thought about it for me we try to only do cool things you know sometimes it works yep I see that's oh my gosh we've come up with the the tagline for the show Welcome to you and I Builder live where sometimes it works and sometimes it doesn't good one yeah this is perfect thank you so much all right um so anything more on logs or should I move on to the profiler stuff uh I think that covers this stuff so yeah let's move on on the profiler okay um so the first thing I wanted to mention there um was the um so by default like in previous builds we um weren't we we were the user was in control of like when we started and stopped recording um so we added this feature to automatically detect when the page loads which is really useful for page load type of uh reload and record type of use cases here so I'll just show one of those here that's another feature that I really appreciate that you guys had put in because it's really hard to tell when something has stopped loading you never know if it's because you broke something or if it's just your internet connection so this is very useful cool um I'm going to do a second one also because some of the stuff involves comparing having to profiles here so you'll get to see it again and it stopped um so the the next thing I want to show is under the table of all the events we've captured we have here a drop down that lets you select the current stuff is list is everything that we had before is all and then you can also see the data broken down aggregated by component uh name here which is similar to what we had in the compare view but it's available here for the more detailed view of the profile um and so speaking of the compare view uh the other stuff I want to show is in there where if you're comparing two different profiles um you'll see here that a bunch of these rows are just all blanks um because that they're showing the differences between the two and so in this case that is kind of not super helpful and kind of noise in a way and so we added a essentially a filter on the table here that let you hide those rows and then filter it down just to looking at the things that actually have deltas in one of the columns oh that makes it a lot more useable yeah and so the other the other thing we did to the table is if you want to see the raw numbers and not just the differences so like the you know before and after if you will of each of those uh previously you would have to expand the rows one at a time and so we added a button to expand everything if you just want to be able to look at all the raw data um and then collapse it all if you don't want to see that anymore oh nice some little little usability improvements um was there anything else we wanted to show for profiler those were the ones I was aware of yeah I think those were the big um small but but big improvements in terms of kind of just usability information that people would have and be able to use okay cool uh that was all I planing demo all right so now I think oh go for it a lot okay oh no I was just going to go over kind of where we're gonna go and kind of share some of that um but if you had something you want to to say go for it no I was just going to say we should try to break something and see uh what the uh tool tells us but please all right fair enough all right so uh okay so what I wanted to share is kind of things and ideas and areas that we're thinking about for 2024 and Beyond uh you know not necessarily um any given release but kind of areas of improvement and kind of areas of focus that we'll have and this is where I think you know we well we would certainly learn loved and appreciate is if there are any of these things that you're like hey this is the most important to me or these are the two or three things that sound like they would be the most valuable for me um you know just just put those in the chat and we can certainly use that information to help us prioritize how we're how we're um delivering things in the future and real quick before that since we're not usually we don't usually show this kind of content on this show we mostly cover the stuff that's already out or very shortly coming out so just again to remind everybody in the chat and in the audience uh this stuff may or may not have a release date and also only make purchasing decisions based off of stuff that's already available um and I think we're good with the disclaimers go right ahead all right sounds great all right so there's really three big outcomes that we're always kind of shooting towards uh one is just improving our runtime performance we want to uh ensure that the experience is built using our next within the next experience and and experiences all of you are building are very performant uh and we want to get really fast page load times just like consumer experiences so three seconds or less out of the box uh is kind of a higher level goal again that's a very big audacious hairy goal for things in service now and data Centric experiences but it's something we want to shoot for we want to increase developer productivity uh so we want folks to save time and money by reusing things that are already in the platform reduce the time it takes to iterate when changes need to happen and prevent development silos uh or or blocking development because there's more than a few people working on it on things and then last but not least you know some of it you saw faster troubleshooting so finding performance and functional in issues in minutes not minutes or hours not necessarily days or weeks um are kind of the three broad areas and things that we want to kind of focus our our feature set and kind of improvements on all right so some of the things that we'll talk about are improving runtime performance there's things where uh we're looking at how do we optimize loading of pages like I talked about some of that is going to be okay well if I'm navigating to different pages Can we cancel blocking transactions because we know you're navigating to another page and we don't need to hold up the navigation anymore uh we're going to look at things of related to prioritizing loading of components so uh kind of for example if there's components that are outside of your viewport and outside of the view do we need to load them at as the pages loading or can we do it more iteratively so that the page is loaded and interactable uh within a shorter period of time we also want to increase developer productivity so we're looking at things like how do we enable things like intellisense how do we enable Frameworks like typescript to improve code quality uh help discoverability help usability of the framework as you guys are developing custom components in particular as well as supporting webpack 5 which will enable faster server start times faster iteration times code changes uh we can take advantage of some things like module caching hot module replacement things like that so again in service of I made a change how do I quickly see it how do I test it how do I get it onto an instance along with that one of the ideas we have is what we're calling fetch from instance which is right now as a component developer if you are creating custom components there aren't all of our great uib components aren't available to you to use within your within your custom components so a important initiative we we're looking at right now is how do we unlock those components to use within custom components and do that consistently so that it's consistent behavior in your Dev servers it's consistent behavior on the instance and you have all of these components that you can now use so you don't have to recreate them and basically the idea behind this is that your instance becomes your npm repo so as you're going from different family releas to family release you're always pulling the versions that are that belong to that particular family release instance or on on that particular developer instance that you have so that way there's not this lag time either of you know hey I I'm developing in a newer family release to validate things versus production is in a different family release kind of minimizes all of those challenges in between and then last but not least some of it is going to be we have this now great now SDK that the uh Team released in uh Washington uh and that's kind of bringing together application development in a single environment uh I think they the example they put on LinkedIn is a the web version of viia uh sorry vs code and so we also want to enable the development experience to be part of that singular service now development experience so we're going to be doing some work there to kind of ensure that it's truly a singular development experience and not different tools for developing comp components versus applications versus something else and kind of really make it seamless and intuitive uh to build all of these things within service now much more easily so that's kind of a however whatever your development workflow looks like we want to support that with custom components so yeah whether you're developing locally in vs code or using the vs code in the in the browser yep that's right nice and of course last but not least we want to continue to improve our next experience developer tools we're looking at things as we talked about some of the indicators are there where we certainly have a lot more ideas on on exposing even more of those types of things in kind of common pitfalls and and failure patterns we also want to look to expose what service workers are doing that tends to be an area that is not very well uh transparent and tends to have issues or or at least leads to uh finding um issues that are occurring so what are service workers doing are they pulling out things from the cash not from the cash Etc uh logs we just talked about server logs we also want to add client logs so again all of the logs are in one place whether it's a server or a client log and another thing we think is going to be immensely useful is actually what we're calling execution waterfall or traces where you can actually see again front end to back end what's uh what's triggering what how long are those different things taking what are the logs related to them uh and even potentially jumping to the code from there to things that you care about so now it's not piecing together information of what's happening but it's actually visually showing you what's happening in what order and how long is it taking to help kind of identify performance issues in particular um and and help with other other things other issues that you may see as well so we're really excited about that one as well and I think that that is the last piece of the puzzle that we're looking into at the moment but these are kind of again High Lev big big areas that we want to go after and we think will be really valuable for all of the folks whether you're creating next experience Pages or developing custom components or somewhere in between there and really excited and looking forward to you know bringing those out for everyone to use cool um well I've got to do aop was at the end of what y'all had yep that's that's that's the big bang right there well I've got some some things we can try to do a little bit of debugging on but I did um we didn't really go over what was you know what was what the changes to the CLI were uh in the Washington release were there any anything big with the CLI changes yeah I I think most most of it was internal for us is kind of updating the the internal engine mainly to support um a more common code base uh we had we had kind of an issue of having splintered code bases for different CIS whether it was within service now or customers were using Etc so there aren't any real functional improvements to call out um but we are setting up the foundation to then now you know kind of build off of and deliver more uh of those kind of things that I had called out around around like you know fetch from instance and and things like that so Washington for us was mainly like building that Foundation to to hopefully deliver these big improvements nice well before we get into anything else does from the from the chat does anybody have any questions or feedback on where they'd like to see this sort of thing go we had a quick question mostly about what uh troubleshooting a troubleshooting question so let's say I'm in impersonating an end user as an admin does that give me the access error yes it does currently um we've we've thought about that use case and had some conversations at this point it seemed a little dangerous to um expose all of that even when you're impersonating but it is a line item for us to go dig into more so right now yes if you impersonate you won't see the server logs because it won't detect you as an admin user makes sense I think that's it for questions we had a few questions about user experience analytics funnel and uib that's not a question that I can answer off the top of my head right now we'll we'd have to look up an answer to that because technically neither are actually my my products but uh we can uh look up an answer if you want to follow up in the SNF slack around the community all right um I guess let me let me share and I have an idea for uh something we can try to do in terms of doing some troubleshooting with the um with the dev tools so let me let me share real quick trying to do set that up I will start with some um quick plugs our thanks Earl I appreci appreciate it our next next experience Academy is going to be on April 17th uh we're going to be going over kind of a everything you need to know to get started and enjoy the content that my team makes um basically it's a great starting point for your cooworker who's trying to get into un Andi Builder live or trying to learn about next experience and any of our products uh it's going to give a very thorough intro to every there so I hope it's a great starting point for a lot of our newcomers and NextGen and other programs um additionally we are going to uh not have any shows the month of May so no next experience Academy and no you and I Builder live in May we're going to be taking a break uh to prepare for and rest from uh the knowledge 2024 conference that's going to happen in Vegas um May 7th through the 9th I'm pretty sure and it's going to be a great time for you guys to go to knowledge. servicenow.com and check out the sessions we have I think like five sessions between you and me Brad uh covering covering everything from introduction to workspaces to here's how advanced theming Works to Brad's uh yearly build a killer blank experience uh lab is coming back um and we're going to be build we're going to be very busy for the next couple months getting all that content ready for you guys so I hope you're able to come say hi at knowledge um if not just remember no shows in May and we'll be back in June was that enough time for you Brad there was yeah fantastic so I'm I I um I'm curious to see whether the uh extension will um will let us uh let us see if we've uh you know put the wrong Json in I I kind of saw uh saw there that maybe it would give us some sort of error uh if the Json is not right but that it's something that I've been uh struggling with a little bit as I build out this knowledge lab um so this is my knowledge lab I think that's probably big enough for everybody but I'm going to zoom in one more time uh which is basically a little note-taking app um but a lot of the things in this app require uh some Json uh in them and so one of them are the drop downs here and it's expecting some specific Json so if I flip back over and we look at these dropdowns where are they here's one um you can see here and I've just hardcoded this in there but you can kind of see if we look at the Json that it expects an ID in a label so I'm kind of wondering will the extension pick up like if I'm passing the wrong Json format or would it be more that I'm like passing a string instead of Json or should we test that I can imagine anything scarier than testing your product live in front of strangers so think we should test it but go for it a lot yeah I mean I I I don't think the extension kind of doesn't know the inputs and outputs of things necessarily so I don't expect it'll catch it but as Gabby says hey you don't know till you try so let's try the hard thing first we don't think this is going to work so like let's let's say what if I pass it like uh Sid and name instead of label we know these are the wrong properties party names so that shouldn't work but let's go ahead and open up here so State too big I have some components that I the state's too big all right so let's go ahead and refresh and see what happens uh so it didn't surface anything new here uh yeah we don't have any I think if if uh it'd be interesting to think through that one a little more I know we don't we'd have to kind of analyze what's happening in the page to kind of figure out an indicator for it because these are kind of like the indicators are basically like known I guess known error patterns and so I don't know if we can tell it's a good it's a good use case it's something we'll have to take back and see if there's an opportunity there um where like inputs and outputs are mismatched or something like that but I'm not entirely sure if we would know that at runtime versus like something that might be interesting to think about as a uib lunter kind of time frame where they're you know so you kind of even know that before you get to kind of like runtime almost nice yeah so we can see it's empty let's let's take a look at what does it tell us if we look at it here um properties let's pop over is that the right no drop down is what we want there we go yeah so if you so it does show us what we passed it it just doesn't know what to do with what we passed it here so that makes sense yeah yeah so you can see exactly right it doesn't know like hey what you're looking for is not matching necessarily um because there's not I'm I'm curious about something here though if you were to uh double click on the item like the the stuff next to that there not not the word items but the the value next to it yeah double click on that um you do see and then you expand the schema on the right side there where it says items a yeah so if you were to try to edit it using the dev tools it would tell you that it's invalid I think but yeah it is telling us what it's expecting here it looks like right ID and label so if we edit it let's let's go back and that is a good point right and then if you click outside of here it should do the validation again yeah oh yeah so it did do it it just didn't surface it right away but I could tell because it wasn't working so if we hit apply will it change it yeah yes just didn't take the label for some reason that's all right interesting but yeah that that that would be the feature in the no that is the label you have them backwards Brad oh did I do them backwards yeah oh I sure did yeah I was just thinking about the tagline right there that's right sometimes it works hey and that looks like it worked there we go that is pretty handy yeah for those of us that were totally paying attention and not chatting about knowledge in the chat could we get a replay on what just happened yeah yeah I can we can Replay by refreshing so what happened was um I I think we I think we've done a better job at this lately uh in that when you have properties on components that are expecting Json and we've done a better job of giving like the Json that's expected in the property but that's it's not always the case and sometimes you've been working with it for a while or somebody else has made some mistake with it uh and so for this one what I did was I came in and I just put in the wrong uh the wrong property names here um so it should be ID and label instead of CIS ID and name and so if if we come and refresh here already I already did it uh we can see that like this component knows there's two things there's two elements in the array but it doesn't know what to do with them so if we come in and take a look at the component uh I know it's the drop down here uh we can see that it does have uh these two uh these these properties here but then when I double click here um um it tells me that something something went wrong right my component's not rendering correctly and it it's basically telling me what the problem is here because there should be an ID for for any properties that have specified this scheme information will validate it whenever you try to save a new value here editing it that is super handy that is pretty handy um so if I hit apply then it will update it for me uh and oh it works now so I can go back into uib and fix it uh the other thing I wanted to test was so we saw on the homepage there was two components here what if we just provide it with uh well let me save it if I do the wrong so if we just H that's too many too many highlights like if I say this this isn't what it want will it let me do that yeah let's see what we get here now so we didn't get any changes here but I'm I'm guessing we would do the same thing at that case we'd go look at it and it would tell us what's wrong let's see oh nothing renders is not rendering yeah and I might have missed it earlier what does State too big mean for that label those are um you can click on click on The View there so basically it's for um State objects that are basically really wide or really deep um so we're tracking essentially how big this Json object or this object is and we want basically when a component has large enough state that it could be a performance concern yeah nice what he said better than me can you explain what a state is like I am five oh when when the when the values that are component specific that are kept track of on a component specific basis grow large enough that operating on them could be a performance concern you got it not bad thank you um actually if we go and by you got it I meant me the 5-year-old brain was able to understand that so thank you I think we uh we we do kind of get into uh State here um so this is what we're talking about I'm not going to like read this to everyone or anything but there's actually a pretty good amount of information uh with the UI framework documentation uh that kind of talks about all of these different concepts and how they work and things like that um so it's probably if you're brand new to it uh if you're already like if you have a lot of background with you know reactive Frameworks this may make more sense I know the first time I read it it didn't make a lot of sense to me and when I come back to it the more I learn the more it makes sense U but it it does uh do a pretty good job of getting into some of these different uh Concepts that and then even in that Dev tools if you if you click that I we did try to try to start doing some more information within the tools so you don't have to go to docs necessarily um if you go back to that homepage there's that little I icon right there the question mark I think the question mark sorry oh yeah there we go oh we try to help describe what some of this stuff is uh I don't know if we described it to the level five-year-old but we gave it a shot no that's fantastic it's okay it's it's okay at least you weren't like my coworker here who totally called me out for not reading [Laughter] documentation that was not my intention it was hilarious though I was just trying to educate people where they could go for more info thank you and now I know what is it developer. servicenow.com that's the one yeah yeah it's back it's wait this way on my little screen can we oh it's not in the frame never mind H forget that that happened um all right I that was kind of the main thing that I wanted to look at um any uh any other questions from the chat uh comments I think we are good on questions and comments all right everything was clear as mud yeah nope everything made sense no no notes um I think Brad you want to go ahead and close it out yeah let's do it all right well thank you everyone for joining uh thanks to uh wolf and a lot uh for sharing uh I I think if you're doing anything with workspaces uib uh you should have this Chrome extension installed um be using it I I've had a couple of instances uh where it really helped me troubleshoot something um I had uh I had an instance where I was talking to somebody and they had built something I hear my oneold yelling at me uh they they had built something and um it was a component where it was expecting one of the properties was a record right and so you just give it a record and it works and then she was dynamically binding data to it and uh so she was binding a CIS ID to it uh directly and it didn't work when we B the CIS ID and so it took some time and eventually we figured out that what it wanted was a little object that had both the display value and the CIS ID uh and so the way that we found that was we we uh hardcoded it found that it works opened the dev tools and then actually looked at what the property was was being passed and it was an object not just a soci as a string um that was a little thing that I don't know how long it would have taken us to figure that out without the dev tools like could have been a couple hours before one of us thought like oh yeah we should try an object there um so again if you're doing anything in uib absolutely you should have the Chrome dead tools extension installed it's definitely super useful and we did get a question in the chat where is the best place to share feedback about the extension oh that is a good question is there a feedback button on the extension uh I'd have I think there is a feedback button on the extension store page but I don't remember necessarily I know we've gotten a couple of uh customers that have left feedback and I'm guessing it's through there so me get back to you so that's one way also if you just find your favorite outbound PM uh we we are always happy to pass along feedback so if you work at a customer you can absolutely give us feedback through your account team you can find us on the community or snev slack or LinkedIn or wherever and pass feedback um but we are always receptive to feedback whether you hate something or you just want to see something in the future uh we want our customers to have the best experience possible using these tools so uh please pass on feedback and uh just a I guess a a selfish plug um I'll be posting a survey in communities to kind of get what you like the most hate the most want to see the most improved in community as well um most likely later today so you know if you have a bunch of things that you're just like I want to get it all out go for it in that way as well so all kinds of ways you can tell us that you love us or hate us or both send us a link and we'll post it in this the description of this uh episode as well all right we'll do yeah well thank you guys so very much for joining us today it has been a fantastic experience I closed out of the stream Brad schooled me on docks we had a lot of fun today uh once again our next episodes we go live every the second and fourth Thursday of every month at 4M Eastern um we are not going to be doing any shows in May and I hope we see you guys at knowledge thank you all so much for watching byebye y thanks everybody [Music] bye [Music] [Music]