> 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/cz-erp-picker/spolecne-informace/konfigurace-aplikace/parametry-konfiguracniho-souboru/sekce-mappings.md).

# Sekce \[Mappings]

Mapování (zápis) do iVlastností souboru Inventoru při volbě příkazu [Zapiš do iVlastností](/erpp/cz-erp-picker/erp-picker-doplnek-inventoru/prehled-prikazu/holixa-erp-picker/zapis-do-ivlastnosti.md) nebo poklepání na řádek v tabulce se nastavuje v sekcích `[Mappings]`.

Syntaxe pro nastavení mapování je "*Interní název iVlastnosti*"="*Název sloupce podle*  `ConnectionSelectCommand`".  Interní název iVlastnosti tedy musí odpovídat některému z názvů iVlastností spadajích do jedné ze čtyř sad iVlastností.

{% 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 %}

### Seznam sad iVlastností s odpovídajícími iVlastnostmi

#### `[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]

* Dle názvu zadaného na levé straně výrazu bude vytvořena, pokud neexistuje, uživatelská iVlastnost.


---

# 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/cz-erp-picker/spolecne-informace/konfigurace-aplikace/parametry-konfiguracniho-souboru/sekce-mappings.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.