> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/clarity-lims/announcements/announcement/customer-notifications/2026-oct-13-lablink-dropdown-custom-field-issue-patch-available.md).

# LabLink Dropdown Custom Field Issue – Affecting Clarity™ LIMS v6.3.5/v6.3.6

Published: 20 October, 2026 Updated: 2 November, 2026

We want to inform you about an issue affecting LabLink dropdown custom fields that is affecting Clarity™ LIMS v6.3.5 (Lablink v2.5.5.13) and v6.3.6 (Lablink v2.5.6.0). Any dropdown custom field configured to not accept custom entries will have all dropdown items shown as unselectable except the default item when creating projects and users in LabLink.

Updated LabLink versions for Clarity™ LIMS v6.3.5 (Lablink v2.5.5.19) /v6.3.6 (LabLink v2.5.6.2) are now available.

We apologize for any inconvenience caused. Please contact Illumina tech support to get the latest version installed.


---

# 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.bioinsight.illumina.com/clarity-lims/announcements/announcement/customer-notifications/2026-oct-13-lablink-dropdown-custom-field-issue-patch-available.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.
