> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/releases/old/3-9-15.md).

# 3.9.15

Release Date: October 12, 2021

## **Store Manager and POS**

### Improving performance of inventory count file import

Starting with release 3.9.15, the method used to load and query the inventory count file has been optimized to improve performance.

### Allowing double-click to drill down on item lookup code

Starting with release 3.9.15, when working with purchase orders and transfers in or out, you can double-click on an item lookup code in the **Code** column to open the Item dialog. In previous releases, you had to hold the **Ctrl** key and single-click in the **Code** column to open the Item dialog. Also starting with release 3.9.15, you can double-click in on item information in any other column to open the **Order Item Card** dialog.


---

# 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://docs.rmhpos.com/releases/old/3-9-15.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.
