> For the complete documentation index, see [llms.txt](https://help.holixa.com/holixa-erp-picker/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.holixa.com/holixa-erp-picker/common-information/application-configuration/configuration-file-parameters/section-mappings.md).

# Section \[Mappings]

The mapping (writing) to the Inventor iProperties file when selecting the [Pick & Exit](/holixa-erp-picker/erp-picker-inventor-add-on/overview-of-commands/be.smart-erp-picker/pick-and-exit.md) command or tapping a row in the table is set in the `[Mappings]` sections.

The syntax for setting the mapping is "*Internal iProperty name*"="*Column name by* `ConnectionSelectCommand`". Thus, the internal name of an iProperty must correspond to one of the iProperty names falling into one of the four sets of iProperties.

{% code lineNumbers="true" %}

```ini
[Mappings_DesignTrackingProperties]
; SAMPLE MAPPING STRUCTURE
    ; iProperty1InternalName=ConnectionSelectCommandField1NameA
Material=Material
[Mappings_DocSummaryInformation]
; SAMPLE MAPPING STRUCTURE
    ; iProperty2InternalName=ConnectionSelectCommandFieldNameB
[Mappings_SummaryInformation]
; SAMPLE MAPPING STRUCTURE
    ; iProperty3InternalName=ConnectionSelectCommandFieldNameC
[Mappings_UserDefinedProperties]
ERPPickerNumber=Number
ERPPickerName=Name01
; SAMPLE MAPPING STRUCTURE
    ;iProperty4InternalName=ConnectionSelectCommandFieldNameD
[MappingsC_UserDefinedProperties]
ERPPickerNumber=Cislo
ERPPickerName=Nazev
; SAMPLE MAPPING STRUCTURE
    ;iProperty5InternalName=ConnectionSelectCommandFieldNameE
```

{% endcode %}

### List of iProperty sets with corresponding iProperties

#### `[Mappings_SumaryInformation]`

* Title
* Subject
* Author
* Keywords
* Comments
* Last Saved By
* Revision Number
* Thumbnail

#### `[Mappings_DocSummaryInformation]`

* Category
* Manager
* Company

#### `[Mappings_DesignTrackingProperties]`

* Creation Time
* Part Number
* Project
* Cost Center
* Checked By
* Date Checked
* Engr Approved By
* Engr Date Approved
* User Status
* Material
* Part Property Revision Id
* Catalog Web Link
* Part Icon
* Description
* Vendor
* Document SubType
* Document SubType Name
* Proxy Refresh Date
* Mfg Approved By
* Mfg Date Approved
* Cost
* Standard
* Design Status
* Designer
* Engineer
* Authority
* Parameterized Template
* Template Row
* External Property Revision Id
* Standard Revision
* Manufacturer
* Standards Organization
* Language
* Defer Updates
* Size Designation
* Categories
* Stock Number
* Weld Material
* Mass
* SurfaceArea
* Volume
* Density
* Valid MassProps
* Flat Pattern Width
* Flat Pattern Length
* Flat Pattern Area
* Sheet Metal Rule
* Last Updated With
* Sheet Metal Width
* Sheet Metal Length
* Sheet Metal Area
* Material Identifier
* Appearance
* Flat Pattern Defer Update

#### \[Mappings\_UserDefinedProperties]

* According to the name entered on the left side of the expression, the user iProperty will be created if it does not exist.


---

# 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://help.holixa.com/holixa-erp-picker/common-information/application-configuration/configuration-file-parameters/section-mappings.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.