> 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/sale-register-cross-tab.md). # Sale Register - Cross Tab Logic ERP has corrected the **DEFINED MARK DOWN** column of the **Sale Register - Cross Tab** when more than one item group level is ticked. The report also runs faster on large runs, and its configuration screen now groups the options under clearer headings. *** ### **Step 1: Open the Report** * Navigate to **Reports/Queries** and select **Sale Registers**. * Open the **Sale Register - Cross Tab**. *** ### **Step 2: Configuration screen** * The report's configuration now opens as one list of options grouped under these headings: **Report Consolidation**, **Report Totals**, **Item Consolidation**, **Item Totals**, **Period Totals**, **Report Layout**, **Quantity & Weight**, **Rates & Valuation**, **UD Net Amount**, **Difference & Contribution**, **Document Filters**, **Party, Agent & Lot**, **Mark Down**, **Other Options**, **Home Delivery Bill Status**, **Txn Type Selection**, **Txn Type Totals**, **Party Group Explosion**, **Party Group Totals** and **Extra Group Options**. * The mark down settings are under **Configuration > Mark Down**: **Item Group Level**, **Party Group Level**, **Mark Down Defined For** and **Mark Down Fillter**. *** ### **What's corrected** * **DEFINED MARK DOWN** now looks for the defined mark down at every item group level ticked under **Configuration > Mark Down > Item Group Level**. Before, only the first ticked level was used, so a mark down defined at any other ticked level was not found. * Because of this, with more than one level ticked, **DEFINED MARK DOWN** can now show a value on rows where it was blank before, and **Mark Down Fillter** can now include or leave out different rows. This is intended. With only one level ticked, the report shows the same as before. * The report is faster on large runs. The figures do not change. * The same correction and the new configuration screen also apply to the **Challan Register - Cross Tab** (**Reports/Queries > Sale Challan Reports**). --- # 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/sale-register-cross-tab.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.