> For the complete documentation index, see [llms.txt](https://docs.dietrichs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dietrichs.com/dietrichs-intelligent-documentation/docs-de-en/design-program/modellbereiche/allgemeines/elemente/sortierung-von-elementen.md). # Sorting of Elements For the ordering of components, it can be determined that ordering is necessary because a change to a component is clearly identifiable. This is not possible for elements, as an element can change without the serial numbers of its components changing, for example if a component is merely moved. On the other hand, sorting the elements after every modification would lead to performance issues. Therefore, the sorting of elements must, if necessary, be triggered manually. The sorting of elements can be invoked in any model area using the function 1-8-6 Element Sorting. As indicated in the following dialog, all elements of all model areas are always sorted. This is independent of the model area in which one is located. If the ordering of components is executed manually or automatically, a sorting of elements is also necessarily triggered. The informational dialog does not appear in this case. This ensures the correctness of the element numbers after a component sorting. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dietrichs.com/dietrichs-intelligent-documentation/docs-de-en/design-program/modellbereiche/allgemeines/elemente/sortierung-von-elementen.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.