> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/ga-releases/release8.2/release-notes/advanced-tools.md). # Advanced Tools ## Query Sheet ### New & Improved ### Improved Query Sheet Processing for Large Columns In the Query Sheet, all columns were processed regardless of their data types. In some cases, very large Data Type columns could increase processing time and affect the overall performance and stability of query execution. With this improvement, Query Sheet (Auto-Mode) can now automatically skip columns identified as excessively large during processing. The behavior can be controlled through configuration when needed. ### Copy Column Names Directly from Query Results In Query Results, users had to download the entire result set to copy column names from the results table, which was inconvenient when only a few column names were needed. With this enhancement, users can now copy column names directly from the Query Results page without downloading the full results file. This improvement makes it easier to reuse column names while reviewing query results quickly. ### Fixed ### Improved Execution of Internal Metadata Table Queries In Query Sheet, an issue in which existing queries against internal metadata tables, such as 'oecolumn,' failed with errors indicating the tables were not crawled has been resolved. This issue prevented previously used data-quality metric queries from running after the migration. The query validation process has been updated to allow these supported metadata queries to execute successfully. ## File Manager ### New & Improved ### Introduced Configurable File Upload Size Limits The File Manager has been enhanced to support configurable file upload size limits, allowing administrators to increase the maximum allowed file size up to **100 MB**. Previously, file uploads were restricted by a fixed size limit, preventing users from uploading larger files through the File Manager. Administrators can now configure the maximum upload size using the **ovaledge.filesize.limit** System Setting. The setting accepts values between **1 MB** and **100 MB**, with a default value of **5 MB**. The configured limit is consistently enforced across all supported File Manager upload interfaces, including Upload File/Folder, Advanced Tool, and File Explorer for NFS sources. File upload screens dynamically display the configured limit, and files that exceed the allowed size are blocked with clear validation messages, helping administrators control file uploads while supporting larger files when required. 👉 For more details, see the [Upload Size Limitation](https://docs.ovaledge.com/release8.2/file-manager/file-explorer#upload-size-limitation) section. ## Load Metadata from Files ### New & Improved ### Expanded Object Type Support in LMDF Sections In the Custom Fields LMDF Template, the 'Sections' tab did not display all supported object types. As a result, users could not find Projects, Project Tasks, and Data Quality Schemes when preparing metadata files for bulk upload. With this improvement, the Sections tab now includes Projects, Project Tasks, and Data Quality Schemes along with the other supported object types. Users can view and select these objects while working with LMDF templates. *** Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA. --- # 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.ovaledge.com/ga-releases/release8.2/release-notes/advanced-tools.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.