> For the complete documentation index, see [llms.txt](https://changelog.impler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://changelog.impler.io/november-2024/v0.28.0-provide-warning-column.md).

# v0.28.0: Provide Warning Column

Now you can keep your data clean without slowing down your workflow. With Warning Validations in 0.28.0, users get helpful alerts without blocking imports.

#### ✨ Latest Features <a href="#latest-features" id="latest-features"></a>

* Column-Level Warning Validations, Adds support for **non-blocking column-level warnings** during data import. Warnings highlight issues without stopping the upload, helping users catch problems without breaking the flow.

#### 🔧 Bug Fixes <a href="#bug-fixes" id="bug-fixes"></a>

* **Check all cell**, Fixed an issue with “Check All Cells” where selecting the checkbox did not correctly select all cells.


---

# 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://changelog.impler.io/november-2024/v0.28.0-provide-warning-column.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.
