Allow reports to be exported from a filtered search. Currently, youre unable to export a report if the results appear from a filtered search, this needs to change.  Show More

Product Autodesk Build / Meetings Meeting Item List View   Purpose To improve the usability of meeting data and increase the efficiency of project management and administrative workflows.   Current Challenge Currently, there is no capability to export information from the Meeting Item List View to external file formats such as CSV or Excel. As a result, activities such as: - Aggregating meeting decisions and action items - Transferring information to reports and progress updates - Integrating meeting data with other systems - Performing cross-project analysis and historical record management require manual data entry or custom-developed solutions. In addition, the current filtering capabilities are limited and do not provide the flexibility needed to support project-specific workflows. Furthermore, users are currently unable to exclude unnecessary meetings from the list. As a result, they must spend extra time searching through a large number of meetings to find the information they actually need.   Requested Improvements 1. Export Function for the Item List Please add the ability to export the contents of the Meeting Item List View to CSV and Excel formats.   2. Enhanced Filtering Capabilities Please enhance the filtering functionality to allow users to filter records based on text values in fields such as the meeting title. Examples: - Exclude meetings whose titles contain "Closed"   Expected Benefits - Easier reuse of meeting data - More efficient reporting and data analysis using Excel - Reduced need for custom API development and manual data preparation - Improved meeting management for large-scale projects - More flexible data extraction aligned with project-specific workflows The Meetings feature is widely used across many projects. Enhancing the export and filtering capabilities would significantly improve productivity and data usability for Autodesk Build users. If you agree with this request, please consider voting for it. Thank you for your support! Show More

I would like to be able to set up a report template and export it to other projects without recreating it. At present, report templates must be rebuilt for each project, which is time-consuming and creates inconsistency across projects. Additionally, further customisation of report outputs is preferred, including PDF and XLSX formats. Proposed functionality: Ability to export and import report templates between projects (or save templates at account level for use across all projects). Expanded customisation options for PDF and XLSX report outputs. Ability to upload a template XLSX file and map report outputs to the required cells. Benefit: If a template XLSX file could be created and the outputs mapped to the required cells, this would allow for more streamlined reporting and ongoing reporting directly from Forma to a master report file. This would reduce manual data handling, minimise transcription errors, and ensure consistent reporting across all projects. Show More

Problem Statement: Project members cannot see report templates that other people have created unless they're an admin.  While we limit the number of admins on projects, we should still allow people to have/use/share the same Report-templates for consistent reporting and to reduce re-entry.   The ask: add a Permissions section to the Reports-settings where you can add a role to see ALL templates, not just the ones created by them.  ALSO, add this Report-setting to project templates, so all projects can inherit these permissions.     Show More

When exporting Issue Detail Reports, it would be great if the headers for each Issue in the report reflected the specific issue, as they do when exported individually.  Show More

Forma allows the addition of custom attributes which is very helpful.  The company moving away from Vault where attributes are used and reported on extensively.  Forma falls considerably short in this effort.  Adding the attributes help future searching after archival of a project and reporting on that information is valuable and essential for good document management. Show More

The possibility for project admin and account admin to always be able to edit report template schedule. If the author left or been removed from the project it's not possible to edit the schedule anymore.  Show More

Looking to be able to take a SNAPSHOT within our cost mgmt in a project everyday. Currently we are limited at 300 per project and would like to be able to do 2 things that are not currently available: 1. would be to allow a SNAPSHOT to be scheduled to be taken daily. 2. Increase the amount of snapshots we can store per project, some projects go multiple years and 300 is not enough. Thank you for your consideration.  Show More

We need the ability to track and report user activity performed through the Autodesk Forma mobile application. Currently, Activity Reports do not provide visibility into mobile app usage, making it difficult for BIM managers and project administrators to measure adoption and verify that field teams are accessing project information. Requested information: - User who accessed the content. - Date and time of access. - Document, drawing, model, or file viewed. - Device source (Web, iOS, or Android). - Mobile application usage metrics and history. - Availability through Activity Reports, Data Connector, and APIs. - Exportable data for Power BI and reporting tools. This functionality would help organizations monitor adoption, improve compliance, and measure the effectiveness of digital construction workflows. Show More

Feature Request:  We would like to have the ability to hide the ID column in the Object Table when grouping is applied. Expected Behavior When grouping is applied, users should have the option to hide the ID column from the Object Table. This would allow users to configure a cleaner summarized view focused on the grouped information and relevant properties, without displaying individual object IDs. For example: Group by Category Group by Family Group by Level Display quantities or other aggregated properties Hide the ID column Business Need This functionality would improve the readability of grouped Object Tables and make them more suitable for: Summarized model analysis Quantity review Model data validation Reporting and presentation High-level model coordination The ID column should remain available for detailed object-level analysis, but users should have the flexibility to hide it when working with aggregated/grouped views. Show More

ACC already captures who approved a review, who commented on it, and when. This information appears in the project-level "Export all" Excel, but it is completely absent from the single-review Review Report — the document most people actually export, share and file as the record of an approval. Please surface the existing data in the single-review report, and expose the reviewer/date fields as proper columns rather than as free text.   The gap – same review, two exports   "Export all" Excel, sheet "Details" — contains: Initiated by Approved by Created on / Finished on Review status per file (e.g. "Approved w/ comments") Comments, in the form Reviewer Name(date, time): comment text Single-review Review Report (PDF export of the same review) — contains: Review name, ID, total / approved / rejected file counts, Status "Closed", Created On, Finished On, Generated By A per-file table: file name, path, version, rounds, markups, issues, review status, action upon completion No approver. No reviewer. No approval date. No comments. So the single-review report — the natural unit for filing, sharing and archiving an approval — is the one export that omits the evidence of the approval.   Requested changes   1. Single-review Review Report — add an approval summary block: Final status Approver Approval date Reviewers Reviewer comments & dates populated from the values ACC already holds. The review-level final outcome should also be stated explicitly — Approved / Approved with comments / Rejected. Today the header only gives "Approved Files n / Rejected Files 0", which does not distinguish "Approved" from "Approved with comments", and "Status: Closed" is a workflow state, not an outcome.   2. "Export all" Excel — split the buried data into real columns: Reviewer name, Reviewer action date and Reviewer comment as separate columns, instead of packing them into a single string of the form Name(date): text. As delivered, this data cannot be filtered, sorted or pivoted without parsing text. An Approval date column for the approver's action, distinct from Finished on. Approver and reviewer company and role. 3. "Export all" Excel — fix the sheet layout: The Details sheet uses a three-row nested header (a merged REVIEWS / REVIEWED FILES / DETAILS banner in row 1, field names in row 2, Original value / New value sub-headers in row 3). Excel AutoFilter, tables and pivot tables do not work against this. Please provide a single flat header row. Status appears twice as a column name (review status and attribute-action status), which makes the export ambiguous. 4. Print-ready single-review export: The individual review export is not usable as an attachment as delivered — column widths, text wrapping and page setup mean it has to be manually reformatted and converted to PDF before it can be shared or filed. Please provide a properly formatted, print-ready per-review export.   Why this matters The Review Report is the record of a formal approval decision, and it is used wherever that decision has to be evidenced to someone who does not have access to the ACC project: Audit and compliance – QA/QMS and ISO 9001 audits require proof of who approved what, with which status, on which date, from a single exported document. Contractual and commercial evidence – confirming that a deliverable or design stage was submitted, reviewed and approved, including as supporting documentation for milestone and invoice approval. Design-gate and stage sign-off records – demonstrating that a gate was passed and by whose authority, for handover packages and for the project's own controlled-document set. Handover and archive – the report is filed alongside the deliverable it approves; a report that omits the approver and the date is not a usable long-term record. Dispute and claims – reconstructing after the fact who approved a document and when, potentially years later and after the people involved have left the project. In all of these cases a report that does not name the approver, state the outcome unambiguously, or give the date of the decision has little evidential value. Because the information already exists in ACC and is already exported elsewhere, this should be a comparatively low-effort change.   The current alternative is to reconstruct the information manually from the web UI, or to extract it from the project-wide Excel and reformat it by hand for each review — neither is practical or auditable, and both push teams into maintaining a parallel sign-off record outside ACC, which undermines the purpose of running the review workflow in ACC at all.   Show More

Add a customizable .xlsx Procurement Log report that can be generated directly from the Submittals tool, similar to the existing PDF report customization options. Users could select and arrange the fields they need, save the configuration as a template, and reuse it throughout the project lifecycle without having to reformat each downloaded report. Including calculated comparisons between approval or closeout dates and key procurement milestones, such as required dates, lead times, and dates required on-site, would provide better visibility into procurement status, help teams identify schedule risks earlier, and significantly reduce the manual effort currently required to produce recurring procurement reports that is already being provided in the platform.   Currently the .xlsx report is not customizable, provides an unnecessary amount of information, doesn't mirror the columns/information we have selected to be viewed in the main submittal log, etc.  Show More

Currently, there is no option to bulk download photos or attachments linked to issues. Users need to access the Issues Detail Report as a workaround to review the attachments. It would be a valuable improvement to have a bulk download option for issue attachments, allowing users to quickly download and review all photos/files associated with selected issues or an entire project. Show More

Currently, exported sheets from Build > Sheets, including issues and markups, visually display the issues, but it is not possible to identify which specific issue is being referenced. Although the exported PDF contains a hyperlink to the corresponding Forma issue, this is only useful for users and companies who have access to Forma. For documentation purposes, especially when sheets are printed, it is essential that the Issue ID is also displayed directly on the sheet. This allows users to correlate the issue shown on the drawing with the corresponding issue detail report (PDF). I am aware that the Issue Detail Report provides an option to include a sheet overview. However, the embedded sheet is only available as a reduced-size overview, and the created markups are not displayed. As a result, it is not suitable for accurately locating and identifying issues on the drawing. We require the ability to export sheets at their actual scale and size, including all visible markups and issues, with a clear display of the corresponding Issue IDs. This would ensure that users can easily locate and match issues within a PDF issue report and maintain a complete and usable project record, even without access to Forma. Below is an example of how we would like exported sheets to be displayed, including the Issue ID directly on the drawing for easy reference and documentation purposes:   Show More

When creating a a report or report template in file format Excel I should be able to remove unwanted Excel columns. Otherwise I have to download the report make edits to Excel prior to submitting the report to the responsible party. There is no point in creating a scheduled delivery of a report if it still has to be manually manipulated and then manually forwarded to the responsible parties.  Show More

Currently, members can share reports with project teams. This creates a risk that incorrect or incomplete reports may be distributed, leading to inaccurate data leaving the system and impacting project decisions. Proposed Solution Restrict report sharing permissions so that only project admins or designated roles can share reports with others. Allow report creators to keep reports personal or submit them for admin review before sharing. Provide configurable project-level settings to define who has sharing rights. Show More

Reports generated by a user are currently visible only to that user, the users they explicitly share the report with, and the project admin. While this provides some control, there is no granular setting to manage who can share reports further within ACC. This limits flexibility for teams that want stricter governance over report distribution.   Proposed Solution Introduce a report sharing control setting that allows the creator to define: Personal (visible only to creator) Shared (visible to selected users) Project-level (visible to all project members) Add an option to control who can share reports further (e.g., only creator, project admin, or designated roles). Show More

Currently, all reports created within a project are saved at the project level, making them visible to every member. This limits flexibility for users who may want to create and manage reports privately.   Proposed Enhancement: Introduce a setting that allows reports to be saved either as personal (visible only to the creator) or project-level (visible to all project members). Default could remain project-level, but users should have the option to mark a report as personal when saving. Show More

In ACC Build, reporting is currently limited to a single hub. Users cannot generate consolidated reports across multiple hubs. This limitation prevents organisations with multiple active hubs from gaining a holistic view of project data, KPIs, and performance metrics.     Show More