> For the complete documentation index, see [llms.txt](https://digitalgarden.batamladen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://digitalgarden.batamladen.com/notes/query-languages/kql/project-or-project-reorder-or-renaming-fields.md). # project | project-reorder | renaming fields ### project The project command shows us just the fields we selected. Because sometimes whole tables can be overwhelming and we maybe need just a few fields from there. ``` VMComputer | where OperatingSystemFamily == "Windows" | project HostName, OperatingSystemFamily, Cpus ``` *** ### project-reorder This command is kinda a spin-off of the project command, it reorders the fields that we specify at the beginning of the table, but does not remove the other fields. ``` VMComputer | where OperatingSystemFamily == "Windows" | project-reorder HostName, OperatingSystemFamily, Cpus ``` As a result the HostName, OperatingSystemFamily, Cpus fields would be at the beginnig and than the rest of the fields from the table. *** ### renaming fields Renaming the fields is easy with the project command. Its just like specifying a variable. Write the name you want before the field name and connect them with = sign. ``` VMComputer | where OperatingSystemFamily == "Windows" | project Host=HostName, OS=OperatingSystemFamily, Cpus ``` As a result, the HostName and OperatingSystemFamily fields would be renamed. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://digitalgarden.batamladen.com/notes/query-languages/kql/project-or-project-reorder-or-renaming-fields.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.