> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/design-data-management-and-exchange/cnc-exporters/cnc-wood-exporters/hundegger-bvx/faq.md).
# FAQ
Frequently asked questions about BVX Exporter
## Can I change the **PART#** assigned to parts in BVX?
There is no way for the user to assign the **Part#** attribute value manually to specific parts in BVX.
The attribute is meant to be used to sort the Parts in a particular order inside the BVX file. By default, the software uses Revit's internal element ID of framing elements as well as the host element to perform this sorting, and if all required information is present, the numbering should start at 00001 and then increment by 1 for all consecutive parts.
| Revit Internal Element ID | Part# |
| ------------------------- | ----- |
| 662412 | 00001 |
| 663516 | 00002 |
| 663621 | 00003 |
You can, however, change how the software does the sorting by choosing any other of the available parameters for the **"Order Framing Elements by"** option in the [Export Settings](https://app.gitbook.com/o/GVtnSLEqyn4gTgkVXno7/s/qtUsszuAWXIZhQhrvjnb/~/edit/~/changes/1837/design-data-management-and-exchange/cnc-exporters/hundegger-bvx/user-interface/export-setup-window/export-settings) tab:
If the software finds missing designated parameter values, Revit's internal element ID will be used instead for those model elements.
---
# 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://docs.besmart.software/design-data-management-and-exchange/cnc-exporters/cnc-wood-exporters/hundegger-bvx/faq.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.
