 Read the question. There's a question from Edwin. Good afternoon. Is it possible to make a field of a SharePoint list increase by itself automatically? For example, the product underscore code field is created only when entering new products. It's an interesting question and I suppose that it depends. What? The famous answer. Do we just start off every SharePoint issue? Every AMA with like, well, it depends. If you are trying to change the field with dynamically. Well, the out-of-the-box SharePoint experience is not going to do that, but if you supplement that with something like column formatting, especially some of those custom JSON examples you can get on the Microsoft GitHub repository, then you can dynamically grow as the string grows, and that's the column width, but you may not be asking that. Maybe you're talking about padding numbers, and adding zeros before and after to try and make a business-type value number. Well, you could use other things like a calculated column or perhaps even Power Automate. What do you think, Sharon? Yeah, I was actually thinking the same thing. One of the really cool new modern features is for list width. It's not automatic, but if you wanted to basically pick the largest item, you can actually pull that width out now in the modern view and save the view, and it'll actually save the width size. It's not automatic, but you can make it bigger, and it will stay that way in the view. But the second example is that, for example, the product code field is created only when entering new products, makes me curious if maybe he's not thinking about the width of the actual column, but maybe instead they're asking if a product is entered, then it shows because the example says it's only created if you're entering new products. That gets me into a dynamic conversation of, is this a forms question, not a list view question, and if it's a forms question, the only way to make that dynamic stuff happen is if you're using Power Apps. That gets into a whole another level of complexity. I read a little bit to that as well, the same thing you did, Sharon, create a field in thinking, I'm going to use the term classic, but I'm not necessarily talking classic SharePoint, of list schema. They thought I'm modifying the list schema at all, which is going to be a really difficult thing to try to achieve in that kind of experience, where you just type the code in and the schema changes. Or as you said, is it just being making the field visible? Or indeed the size, there's so many options there. Then we can even talk about managed metadata. I've done a couple of different projects using a mix of SharePoint and Power Apps with managed metadata where you can essentially have an option for them to add new fields, or new terms to the term store. Let's say we've managed metadata field, and as we have new products, we show what the existing products are, and we can also add new products to that using a term store. So all kinds of different ways you can go with this. I know Mike just the other day was, tell me about some fantastic thoughts that he had on the SharePoint platform submit. Oh yeah. We love SharePoint. As the resident expert.