> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/praca-z-komponentami-bazowymi/zasilanie-wartosciami-z-zewnetrznych-zrodel/podpiecie-slownikowego-zrodla-danych.md). # Attaching a dictionary data source Eximee allows form components to be populated with data from *dictionaries* — that is, predefined lists of values maintained in **the** platform. Dictionaries are convenient for drop-down lists or radio button groups, as they centrally manage sets of options (e.g. a list of countries, a list of document types). Updating a dictionary in one place can automatically affect all applications using it. **Step-by-step configuration:** 1. **Preparing the dictionary:** Make sure that the required dictionary has been created in the system (in the **Dictionaries** Eximee library module). Check whether it contains the current keys and values, and if necessary create a new dictionary according to the requirements (e.g. CountryList with country codes and names). 2. **Selecting a component:** In Eximee Designer, select the component that is to be populated from the dictionary. These can be: **List value selector** (Combobox), **Text field**, **Radio group** or **Checkbox group** — all these types support dictionary sources. 3. **Selecting a dictionary as the EDS:** In the **Properties** → **Interactions** of the component, click in the **External data source** and select **Select a service**. In the list of available sources, find the name of the appropriate dictionary. The dictionary appears on the list just like services. After selecting the dictionary in the **External data source** field, its name will appear.

Figure 1. External data source selection window with the selected dictionary

4. **Parameter mapping (conditional dictionaries):** For a standard dictionary (without conditions), no mapping is required — the component automatically retrieves all keys and values. However, if a conditional dictionary is used, parameters will appear in the **Input parameters** tab that need to be mapped. These are usually other form fields on which the dictionary content depends (e.g. the Cities dictionary depends on the selected Voivodeship). In such a case, assign the appropriate components to the parameters, similarly to service input mapping.

Figure 2. Example of mapping input parameters for a dictionary with defined conditions for displaying keys

5. **Save:** After finishing the configuration, save the changes. While the application is running, the component will be automatically populated with data from the dictionary. In the case of a conditional dictionary, the list of values will be refreshed automatically when the field it depends on changes (e.g. changing the Voivodeship will reload the Cities list). ### Attaching a script A script service can also be the data source for a component fed from a dictionary source. This solution makes it possible to write a script that can, for example, calculate dictionary values depending on an input parameter or return different values for different languages.

Figure 3. Example script returning a dictionary with input parameters

--- # 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://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/praca-z-komponentami-bazowymi/zasilanie-wartosciami-z-zewnetrznych-zrodel/podpiecie-slownikowego-zrodla-danych.md?ask=&goal= ``` `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.