> 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/baudatenprogramm/baudaten-exceluebergabe/export-aus-baudatenprogramm.md).

# Export from construction data program

## Construction Data Excel Transfer

There are two cases for which file is written. If a file with the name of the target file already exists, it will be overwritten. If the target file does not yet exist, the source file is used and copied.

<figure><img src="/files/89c1ce302ed53c54a8469eb97fdf767cd461f682" alt=""><figcaption></figcaption></figure>

In this case, "ErgebnisListe" is used as the name of the target file. This list does not yet exist and will therefore be created from the source list.

Project information, measured quantities and material lists can be transferred.

Using the browse button behind the respective settings, we can change the settings. Thereby we determine which information is transferred and into which cell or range it should be written.

* Browse button for "Project information"
* Button "New"
* Browse button at Variable -> select project number

Via the cell reference we control the target cell or target range.

* Browse button cell reference
* Named range -> project number

The range "Project number" has already been defined in the Excel file and can be selected here. The export thus reads these ranges from the source file. Because the range is selected rather than a fixed cell, the range can be moved in Excel without the reference in the Excel export needing to be changed.

* Create project variable with named range

In this case the data type is "Text". This can be decisive if a value is to be further processed in formulas in Excel.

* Check the box at BDP position

### Measured quantities

* Create measured quantity for coverage area

In the browser for the measured quantity, the button "New" on the right can be used to select from which variant the information will be transferred. If this is not used, all variants are transferred.

Measured quantities can be aggregated/divided using 3 different variants.

* Building element: Create a separate row for each building element.
* Measured quantity sum: A row is created for each variant. Values contained for the building elements are already summed.
* Total sum: The sum of all selected variants is formed

The cell reference is again chosen here via the named start and end range.

<figure><img src="/files/7b0615e582629125c18fbfa7b60a7eb89e56cb7d" alt=""><figcaption></figcaption></figure>

In addition, it is determined which information of the measured quantity is transferred. This populates the cells below and to the right of it.

* "New" and create building element type as well as building element number and measured-quantity value

The order determines the sequence of the columns to the right.

<figure><img src="/files/6babf70eb38b82b196dbea8d9bf8aa7d5a118bd5" alt=""><figcaption></figcaption></figure>

* Create additional measured quantities for formwork area, as well as the lengths of eaves, ridge lines, verge edges, hip lines and valley lines using the same procedure

### Material lists

For material lists the entire material list is transferred. The column setting that can be configured for material lists in the construction data program is used. It is therefore advisable to always create material lists with the same identifier. For example H01 for the timber list.

* Select material list BDP
* Setting "Excel Export"
* Confirm setting

The Excel list is created with the "Ok" button.

<figure><img src="/files/2cb1cd7e9208fa4fa010896287c429e7b67dde36" alt=""><figcaption></figcaption></figure>


---

# 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/baudatenprogramm/baudaten-exceluebergabe/export-aus-baudatenprogramm.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.
