# v0.17.1: New Select Input, Updated readme, contribution guide, and Improved file parsing! ✨ New * Introducing a new select dropdown feature designed to seamlessly handle extensive lists of select values, ensuring smooth performance during validation. * Implemented a migration script for effortless updating and saving of template files with the latest schema. Find the migration guide [here](https://docs.impler.io/additional-resources/data-migrations). * Rolled out an intuitive onboarding flow for new users, providing them with a comprehensive understanding of the platform's functionality. ➕ Improved * Enhanced developer experience by refining setup scripts, minimizing build errors, and reducing the dependency on external packages through the integration of in-app solutions. * Optimized data validation views by intelligently truncating lengthy text within cells, facilitating clearer data analysis. 🔧 Fixed * Resolved an issue where the default value input in the column adding form displayed a different focus color, ensuring a consistent user experience. * Addressed the problem of missing Nx modules, ensuring seamless integration and operation. * Fixed the Excel parsing mechanism to handle large numbers accurately without formatting discrepancies. * Improved Excel parsing efficiency by optimizing the timing of value extraction from the end of rows. We’re constantly working on improving the way 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 have a chat with us and share your thoughts! --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://changelog.impler.io/march-2024/v0.17.1-new-select-input-updated-readme-contribution-guide-and-improved-file-parsing.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.