> 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/december-2023/v0.13.0-record-grouping-latest-dependency-upgrades-and-bug-fixes.md).

# v0.13.0 - Record grouping, Latest dependency upgrades, and bug fixes!

With an improved version of the review layout users can group records, applications use the latest version of dependencies, and important bug fixes for a smooth data import experience!

### ✨ New

* Introducing a grouping facility for the review phase, users can jump among `All`, `Valid` and `Invalid` data tab to quickly see records in the respective category.

### ➕ Improved

* Upgraded `next` & `axios` version in `web` and `demo` applications.
* Ignored `max-len` warning in Table and build warnings for building packages.&#x20;

### 🔧 Fixed

* In the code editor, when trying to access the undefined variable, the validation method was returning an internal server error.
* Unique item validation was not working properly when re-validating the data.
* If the user has not mapped any column, then the review phase was showing `undefined` in every cell for that column.
* Improved data rendering mechanism to decompose tooltips when rendering fields to avoid data inconsistency.
* The errors were getting updated at the wrong index when the user changed the cell value at the first index.

We’re constantly working on improving the way handle CSV & Excel import in your product, and value your input on features, bugs, and more. Make sure you join [discord](htts://discord.impler.io) to have a 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/december-2023/v0.13.0-record-grouping-latest-dependency-upgrades-and-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.
