> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-version-release-notes/october-2026/reports-queries/sale-registers/retail-store-lease-details.md). # Retail Store Lease Details Logic ERP has corrected how the **Retail Store Lease Details** restores its default field captions. Restoring the defaults now puts every caption back against its own field. The report's configuration screen has also been updated. *** ### **Step 1: Open the Report** * Navigate to **Reports/Queries** and select **Sale Registers**. * Open the **Retail Store Lease Details**. *** ### **Step 2: Field Captions** * Go to **Configuration > Report Options > Field Captions**. * Tick **Field Captions** to open the **Field Captions** window, where you can rename any report field as it should appear on the report. * Untick **Field Captions** to put every caption back to its stock wording. This takes the place of the old **Restore Default** button. * Captions can be renamed, but not left blank or used twice. If a caption is blank or repeated, the configuration is not saved and a message tells you which row or caption to correct. *** ### **What's corrected** * Restoring the default captions now puts each caption back against its own field. Before, the **Restore Default** button added six extra captions in the middle of the list, so the last nine fields of the report showed the wrong captions. * If you used **Restore Default** earlier and some captions now look wrong, untick **Field Captions** and save the configuration again. --- # 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://kb.logicerp.com/logic-erp-version-release-notes/october-2026/reports-queries/sale-registers/retail-store-lease-details.md?ask=&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.