> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/releases/2023/2023.18.0-august-29-2023.md).

# 2023.18.0 - August 29 2023

### Bugs/Cases

* DEV-973 Data Tables getting duplicated rows after migrating
* DEV-1004 Calendar not working after backspacing on selection
* DEV-1053 Not being able to see Data Tables even if you have the correct permissions
* DEV-1120 Renders Page not loading properly
* DEV-1122 Metadata queries causing significant slowdown
* DEV-1123 Large datatables causing crashes when viewed
* DEV-1133 intermittent 404 errors on catalog items during navigation
* DEV-1134 500 error when searching datatables by name
* DEV-1135 Metadata queries not returning correct result


---

# 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://community.threekit.com/releases/2023/2023.18.0-august-29-2023.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.
