> For the complete documentation index, see [llms.txt](https://help.besmart.software/erpp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/erpp/common-information/application-configuration/configuration-file-location.md).

# Configuration file location

Configuration files for Holixa ERP Picker are located in the following directories:

* Be.Smart ERP Picker (Inventor add-in): `C:\Users\Public\Documents\ArkanceSystems\ErpPicker4Inv\`<mark style="color:blue;">`ErpPicker4Inv.ini`</mark>
* Be.Smart ERP Picker (standalone application - ErpPickerApp.exe): `C:\Users\Public\Documents\ArkanceSystems\ErpPickerApp\`<mark style="color:blue;">`ErpPickerApp.ini`</mark>

The location of the configuration files for both versions of the add-on can also be set using the registry entries in branches `Computer\HKEY_CURRENT_USER\Software\ArkanceSystems\`<mark style="color:blue;">`ErpPicker4Inv`</mark>, resp. `Computer\HKEY_CURRENT_USER\Software\ArkanceSystems\`<mark style="color:blue;">`ErpPickerApp`</mark>.

In this case, it is necessary to create a `Settings` key in the branches above and add a new string value `ConfigFullFileName` with the required path to the \*.ini file.

<figure><img src="https://content.gitbook.com/content/FYRFlm10rTQEBxnOV2DT/blobs/NjcBUTWJGsoKaEDKKsp4/image.png" alt=""><figcaption><p>Setting the path to the *.ini file in the registry</p></figcaption></figure>

If no valid value is specified in the registry, the location from the default directories is used.

{% hint style="info" %}
Changing the location of configuration files in the registry is not strictly necessary.
{% endhint %}


---

# 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://help.besmart.software/erpp/common-information/application-configuration/configuration-file-location.md?ask=<question>&goal=<user_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.