 I did see one question that came in, or it was a more suggestion, came in as a direct message to me here on Zoom. The question earlier was whether there was an option for count in queries, and the recommendation was that it's not a great one, but when you use a page resource, you do get back a total count with that response. It shows you not only the first one or 10 or 50 items, but it also tells you in the pager response, if we look here. In this pager, we have total, so if we get rid of this filter, we can actually show that there are 437 total objects here. So that's a good suggestion that is a way to get the total count of resources. It doesn't always work though. I will warn you because in particularly for tracked entity instances, sorry, I wasn't sharing my screen so you couldn't see that. So here, this is what I was showing. So I have just the listing all visualizations, but with paging, so we have in the response, we have this pager block as we saw before. We're on page one, we have nine pages. This total is the total count of the number of visualizations in this system. So that is one way to get the count of visualizations and you can also get the count for with a particular filter applied or something like that. So filter is type equals single value. We should have nine, I think it was of these. So we have 10. We have 10 because I created that I am a test. So we have 10 total visualizations that match this filter. That is a little bit hacky, but that is a way to get the count of objects. The challenge there is with tracker. So particularly for tracked entity instances and some events, because there could be many millions of tracked entity instances or people tracked in a system, it is very expensive for the server to calculate the total count for every response. So for those endpoints that total count might be an approximation, it might not be the exact number. So just keep that in mind. Okay. Thanks. Thank you. Thank you. Good question. Or good, good suggestion, Alexander. I reposted a question in Slack from Mokaila in the Academy channel. Should I read it for you? Can we install the HS2 slash UI and the runtime in next JS up? I can respond to that one. So the answer is yes, but I would not recommend it. I mean, you definitely can. So UI and runtime are both libraries that can be used in any system. They don't require the platform to be used. But there are a lot of things that the platform will give for you automatically that I would recommend using the platform. And if you have specific features of next JS that you would like to see implemented in the platform, that could be something that we could discuss. So short answer, yes, you can use UI. Absolutely, you can use that UI in any React application. You can use runtime also in any React application, but you have to initialize the provider yourself. So you have to specify the React context provider with the base URL, the API version, and some other things for that particular instance in your application, which you don't have to do if you're using the platform. But you could also get a lot of the features of next JS in the platform, and we're looking to add more things like file-based routing and potentially server-side rendering and server-side functions as well in the not too distant future. So if there are specific features of next JS that you would like to see in DHS2 applications, I would love to hear what those are and why you would like to see them or use them. Thanks. Thank you, Austin. Is there any other questions? Maybe after I introduce the exercises in the project, we can open to Q&A, also a session where you can unmute yourself and feel free to ask any questions. So again, the exercises for this session for the up runtime are in the folder workshop one. The first one was the query, and then you can check mutations here, and you get the readme file with the information. I'm going to show you in my code editor what you have to do, but basically here is just implementing what Austin has showed, delete, and create. So not update this time. And I will show you how it looks. So you have the source code here, and inside the components folder, there are a bunch of components, but you only have to worry about the delete visualization button and the new visualization button as well. So for the new, this is asking you to create a query, to create a test. I'll show you how it looks on the browser. And then for delete, this is a type delete, of course. And if you want to get more information on, want to see some examples, you can go to use the documentation, and here are some examples. So this one, this is for delete, and then you get here for update and create. The plan again is to add more of these examples. This is a create one, just as a reference. So you know that it's there, you can consult this documentation. And feel free to, this is optional, maybe if this is too much, don't feel pressured to do these exercises, but it should be, it's already set up for you there. And the way the way we look after you're done is like this. So here you will be able to delete, as you can see, and to create a new visualization. And there is a folder with a solution as well, if you get stuck. And I think this is, this covers the exercises section and the up runtime. We hope that it's, that it was clear that it wasn't too much, but it's very important to know, of course, how to use the API, the DHS, the API and how to interact with it on your applications. And hopefully the up runtime would facilitate that process as you're building your applications. And I think, should I go over the project now, or I'm not sure because of the recording? We can have it on the recording now. Do you want me to make a new recording just for this or not for you? Okay, no, I think it's okay. Yeah, keep it with the questions. Good, good. Okay, so again, in the same template, we have created a projects folder. And if you go to project one, you will get some information on this. And this is not required, of course, for this, for workshop one, but for participants who are joining us on the advanced workshop two in May. It's, it is required that you finish this project. So, and that you will build on this project as your, what, when you do project two for the certification. So for, for the, for participants who are just joining today, and not for the advanced one, feel free to do this as well. It's, it should be, it should cover the topics that we, that we had discussed yesterday and today. You will see the requirements is what we've done yesterday to create an application sidebar. So most of the, the exercise that you've done for the UI library. And as for the runtime, the only requirement is to use data query. And it's optional to use mutation components, if you want. And this is the deadline. So we would like to get those projects before the, before we start with the workshop number two. And like I said, you would build on this project for, for project two, if you join the advanced, and this will give you certification as well. So if you have any questions about the projects, also you can ask on Slack. I believe that all the information is here, you can, you can check afterwards. And we look forward to seeing your projects. And to see if it's, yeah, just to get the feedback, if it was too easy or too hard. Yeah, we would like to, to know what you think. And I think that should cover the sessions, but I, I would like to open the room for, or the floor for, for Q and A just about anything really.