# Mapping Field Types

The following tables summarize the mapping of UDF/custom field types.

| **Field Type**     | **Groovy Data Type**                            |
| ------------------ | ----------------------------------------------- |
| Text               | String                                          |
| Multiline Text     | String                                          |
| Text Dropdown      | String                                          |
| Hyperlink          | String                                          |
| Hyperlink Dropdown | String                                          |
| Toggle Switch      | Boolean                                         |
| Date               | Date                                            |
| Numeric            | double, float, log, int, BigDecimal, BigInteger |
| Numeric Dropdown   | double, float, log, int, BigDecimal, BigInteger |

## Working with Toggle Switches

The LIMS and API treat the toggle switch field type as boolean when its value is set to true or false. However, it is possible to configure a toggle switch to not have to set a boolean true / false value. In this case, the value of the field is *None Set* and the field is treated as a 'nonexistent' field. To make sure that a toggle switch value has been set, you can use the *hasValue* function. For details, see [Handling Non-Existent UDFs/Custom Fields](https://help.connected.illumina.com/clarity-lims/integration-toolkits/lltk/lltk-specifying-custom-fields#handling-non-existent-udfscustom-fields).


---

# 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://help.connected.illumina.com/clarity-lims/integration-toolkits/lltk/lltk-working-with-the-script/lltk-mapping-field-types.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.