> 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-2023/v0.12.0-introducing-data-cleaning-unique-check-improvements-and-some-bug-fixes.md).

# v0.12.0 - Introducing Data Cleaning, Unique check improvements, and some bug fixes!

Excited to announce our best release where users can edit their data from widget itself, along with validation improvments!

### ✨ New

* Introducing a data cleaning facility where users can edit the invalid data in the widget itself, instead of downloading the data and editing them manually.
* Improved easy schema editing facility so developers can add columns all at once, without lifting the mouse.

### ➕ Improved

* Made a unique check validation to ignore empty values. so if the column has more than one empty value editor will not throw an error for duplicate empty values.

### 🔧 Fixed

* Made regex data to be visible and editable in the bulk schema editing section in the table.
* Fixed widget pagination not updating when updating cell values.

Thank you for reading so far! We’re constantly working on improving the way we handle CSV & Excel import in your product, and we value your input on features, bugs, and more. Make sure you join [discord](htts://discord.impler.io) to chat with us and share your thoughts!


---

# 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-2023/v0.12.0-introducing-data-cleaning-unique-check-improvements-and-some-bug-fixes.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.