# Localized Values

## Possible Entity Keys

Localized values import templates supprot keys from entity that you are using mapping for.

{% hint style="warning" %}
Your entity key must be unique. If you have two products with same Name fields, you will not be able to use Name as entity key.
{% endhint %}

## Column Destinations

{% hint style="info" %}
Altohugh category has many different column destinations, we would describe only ones that have special functionality.
{% endhint %}

<table><thead><tr><th width="231">Column destination</th><th>Explanation</th></tr></thead><tbody><tr><td>Key</td><td>The value that you selected as entity key for this template.</td></tr><tr><td>LanguageId</td><td>ID, Name of a language, or Language Culture. <br><br>You need to create language in nopCommerce first. Go to Configuration -> Languages.</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://importmanager.docs.foxnetsoft.com/column-mappings/localized-values.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.