> For the complete documentation index, see [llms.txt](https://docs.truedat.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truedat.io/v8.4/release-notes/v6/v6.9.md). # v6.9 ### Features and fixes delivered with this release ### Features * TD-6649 In concepts downloads include the domain name. ### Fixes * TD-6659 Permissions error when requesting a grant for another user. * TD-6650 Fields of user type not displaying correct list of users when creating a new concept. * TD-6716 Information of concepts fields in secondary language not displayed. * TD-6689 Concepts tab not being displayed in implementations details for non-admin users. * TD-5149 Structures tab in implementations is producing an error in case that implementation is linked to a deleted structure. * TD-6317 Improve performance of queries to retrieve nodes in linage. * TD-6602 Invalid redis representation for updated roles. * TD-6307 \[PVR0499052] Vulnerability in follow-redirects-1.15.2.tgz. * TD-6739 The column "Has note?" in the fields table is always "Yes". * TD-6733 Error processing implementations that are related to rules . * TD-6734 Error on Business concept download . * TD-6742 Concepts graph relations is not working. --- # 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.truedat.io/v8.4/release-notes/v6/v6.9.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.