> 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/january-2024/v0.15.0-default-value-forward-slash-and-more.md).

# v0.15.0 - Default Value, Forward Slash and more!

We've added facility to duplicate import items, paginate and search over them, and few bug fixes!

### ✨ New

* You can provide a default value in the column. You can use provided macros like `null`, `undefined`, `[]`, `true` and `false`. Or you can mention a value of your choice. Which will reflect in response when the column value is empty or undefined.

### ➕ Improved

* You can provide a key for `Handsontable` dynamically from environment variables while self-hosting. By default, the impler uses the trial license key.

### 🔧 Fixed

* The error mapping was not working properly if the column key contains `/`. Now you can use it without any hesitations.
* The import widget was not able to manage the data count properly due to an incorrect API response.
* Backspace on any cell in the import widget was showing `null`.

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/january-2024/v0.15.0-default-value-forward-slash-and-more.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.
