> 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/maschinenuebergabe/abbundmaschinen/automatische-dateinamen.md).

# Automatic file names

The file names are generated automatically. For this purpose, the file name is also determined using variables:

* The variables are written using **#** and can be formatted: **#ENr\[,,0,4]#** means, for example, that the wall number (variable **ENr**) is padded on the left with zeros to 4 digits. For the wall number **23** thus is **0023**. (See also the chapter on the new formatting options for variables).
* Multiple variables can be combined. **#Project##ENr\[,,0,4]#** yields in the project **20001** for wall 23 the file name **200010023**.
* The variables can also be combined with fixed text. **#Project#\_Wand\_#ENr\[,,0,4]#** yields in the project **20001** for wall 23 the file name **20001\_Wand\_0023**.
* User variables from the project's default values can also be used for the file names.
* Variables in the file name and file partitioning must be combined sensibly. For example, you can only use the wall number in the file name if the output is also partitioned according to walls. Below you will find a corresponding listing.

Entries for the file names can also be stored in the file **%dhpvor%\path.vor** in the section **\[FILENAME]** %DHPVOR% is a subdirectory in the installation directory (e.g. DIETRICHS21) and the subdirectory for German installations is WINVOR\GER. The entries in the \[FILENAME] section are offered when you expand the input field for the file name.

Possible variables for the file name and possible combinations with file partitioning:\
\&#xNAN;*all into one file* = **all**, *file per building element* = **gew**, *file per element* = **elw**, *file per package* = **paw**.

> **V\*** User variables\
> from project default values (**all**, **gew**, **elw**, **paw**)
>
> **Project** *Project number* (**all**, **gew**, **elw**, **paw**)
>
> **ConstructionSite** *Construction project* (**all**, **gew**, **elw**, **paw**)
>
> **Info** *Construction project comment* (**all**, **gew**, **elw**, **paw**)
>
> **Position** *Position number* (**all**, **gew**, **elw**, **paw**)
>
> **PositionsInfo** *Position info* (**all**, **gew**, **elw**, **paw**)
>
> **SWAKT** *current floor* (**gew**, **elw**)
>
> **SWAKTNUM** *number of current floor* (**gew**, **elw**)
>
> **ENr** *Wall number* (**gew**, **elw**)
>
> **EENr** *Element number wall* (**elw**)
>
> **EAf** *Execution wall* (**gew**, **elw**)
>
> **ETyp** *Wall type* (**gew**, **elw**)
>
> **EzTyp** *additional wall type* (**gew**, **elw**)
>
> **D\_AUSF** *Execution ceiling* (**gew**, **elw**)
>
> **DNr** *Ceiling field number* (**gew**, **elw**)
>
> **DENr** *Element number ceiling* (**elw**)
>
> **F\_AUSF** *Execution roof surface* (**gew**, **elw**)
>
> **FNr** *Roof surface number* (**gew**, **elw**)
>
> **FENr** *Element number roof surface* (**elw**)
>
> **PANr** *Package MOS* (**paw**)


---

# 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/maschinenuebergabe/abbundmaschinen/automatische-dateinamen.md?ask=<question>&goal=<endgoal>
```

`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.