It would be extremely valuable to have dedicated Files/Documents and File Versions data available through Data Connector, containing all files stored in Forma Data Management along with their associated metadata and version history.   The export should ideally include key information such as: File and folder ID Lineage ID Version ID File name and extension Full folder path Version and revision Status Created / modified dates and users Custom attributes and metadata Naming standard attributes Review and approval information where applicable File relationships and references where available   A particularly important requirement is access to metadata at the individual file version level.   Today, the File Log export primarily provides information about the latest/current version of each document. However, for proper document control and historical reporting, we need to be able to access every version of a document and the metadata associated with that specific version at that point in time. This would allow us to understand how a document and its metadata evolved throughout the project, including changes in revision, status, classification, attributes, and other information.   Today, Data Connector already provides access to a large amount of project data, but there is no simple way to retrieve a complete and structured dataset of project files, their versions, and their metadata.   Interestingly, document lineage IDs are already exposed in some Data Connector relationship tables, but without a corresponding Files/Documents dataset, these IDs are extremely difficult to use effectively for reporting and data integration. This capability is especially critical for major infrastructure and large-scale projects, where tens or hundreds of thousands of documents and potentially millions of versions may be generated throughout the project lifecycle.   If exposing this volume of data creates performance or scalability concerns, this capability could potentially be restricted or enabled selectively for specific projects. However, for major projects operating a data-driven CDE, access to this information is essential. This is particularly important for CDE management, ISO 19650 workflows, document control, auditability, data quality monitoring, and BI reporting.   Having Files/Documents and their version history available through Data Connector would allow teams to build automated document registers, metadata compliance checks, historical reporting, dashboards, and data-quality controls directly from the CDE, without relying on custom APIs or manual exports.   For a data-driven CDE, documents, their versions, and their metadata should be as accessible for reporting as the data from other Forma modules. Show More

Our team has noticed some gaps in the Files Packages tool. This tool has the potential to be extremely useful, but the current limitations make it difficult to implement. Our suggestion are: 1. Enable all file metadata and custom attributes to be edited just like they are in the Files-Folder view.  2. Every feature that is available in Files-Folder under the three dots menu should be available in Files-Packages (especially the move, copy, rename functions)  3. All data for Packages should be exportable from the root view of the of the Files-Packages window, and this export should also include a list of files with their versions that is hyperlinked.  4. Custom fields should be added for Packages that can be edited in the Package itself or the root view.  5. you should be able to create a reference for package, or multiple packages (through multi select and a bulk action) in the root view. References should be to every item in the software, including Meeting Items.  6. There should be some way to view packages from desktop connecter, either in the data connector or some other user-friendly window. Whatever the menu or tool looks like it should allow for editing in the native desktop app of the file.  Linking to a similar suggestion: Edit Attributes of Files inside packages - Autodesk Community  Show More

I work with the Product Team at OpenSpace. We are interested in developing a feature that would allow customers to automatically create an Autodesk-integrated OpenSpace project whenever the corresponding project is created in Autodesk.   At this time, it does not appear that Autodesk provides a webhook API event that notifies integration partners when a new project is created. Without this webhook, we do not have a reliable way to monitor for new Autodesk projects and trigger the creation of the associated OpenSpace project.   We would like to request that Autodesk make a project-created webhook API available so that we can build this functionality and better support automated project setup for our mutual customers.   I imagine this would also be very useful for other integration partners or customers who would like to build automated workflows downstream from Autodesk project creation events. Show More

Please provide the ability to utilize/access the Budget Snapshot data, not just current data, through the data connector and an API. Show More

When adding adding additional attributes in reviews are not added in the data tables of ACC. For several reports, the additional data is required.  You can make an extract of the data, and there the data is available, so why not in the data tables. T Show More

The current last_sign_in date only shows the date for BIM 360, not Build. Please add a last_sign_in_build date for Build or change the process so the existing date reflects the users last sign in date on BIM 360 or Build. Also, add a last_sign_in on the admin_project_users extract table for the last time that user accessed each project. Show More

The current setting of data refresh of 5am and 5pm for EU servers is not sufficient to actively track activities. We currently try to track completion of sections in forms. If a colleague completes their section it will not be shown until the next morning that this section is complete. We would like to increase the data refresh time - the best case would be a "live tracking", however, at least 2-3 more updates during the day would already be helpful. Show More

PLEASE improve sending links to files/folders with the desktop connector. The web only link is mostly useless IMO. A simple addition of "Copy Local Link" .   Show More

We are trying to extract Reviews data and Files' & Packages' data into Power BI using the ACC Data Connector, but it does not provide the same level of detail as the reports generated directly from the Reviews tool or the Files tool. For reviews' data, we are specifically missing information such as the name of files, their associated dates, individual approval statuses, file path and the before-and-after values of the file attributes. Manually generating these reports each time for dashboard creation is not sustainable, and we require this data to be accessible through the Data Connector. Similarly, the connector does not extract data with the same granularity as the Files Export report. We request that these capabilities be added to the Data Connector as soon as possible to support our reporting needs. Show More

I am trying to pull all the comments in a Submittal, either in reviews or responses in all revisions. Currently the comments on previous revision is not accessible. Based on Autodesk Customer Service response, those data are available in TaskRevision and StepRevision tables which are not accessible through data connector.  Show More

On several occasions it would be beneficial to have files log (report) in the dataset extraction from ACC to enable it for Power BI and Insight builder.  Should be easy to add this information to the datasets.  Show More

RFIs have a variety of applications. At time questions are submitted for review that aren't necessary. These unnecessary RFIs then dilute the reporting, and status of RFIs which are legitimate. There needs to be an RFI status where the "reviewer" can provide a response that states something like: "Refer to contract documents", or "Included in Plans and Specs" etc. This is necessary to avoid the dilution of RFI status reports with information that could appear as "Open". They also drive up the number of RFIs and required additional resources for review and response - through normal workflows. Show More

In BIM 360, 5 years ago, rooms were visible in 3D. After it was deactivated. (In power BI, with the SVF viewer, it's possible to see in 3D the rooms). Autodesk now has a stragegy for the data inside ACC. Rooms elements have a lot of useful data for client, designers, construction teams... (area, perimeter, finishes, department...), these data are useful to track the program, the finishes quantities... and to track the work progress on site. It would be great and really useful to have an option to enable the display of rooms in the viewer (3D & 2D). Show More

Problem Statement The Autodesk Construction Cloud (ACC) Data Connector for Reviews does not provide individual file-level review status information. As a result, users are unable to access the status of each file within a review (e.g., Approved, Approved with Comments, Rejected) through the connector, making it difficult to create comprehensive custom dashboards and reporting in Power BI without relying on manual exports from ACC. The required file-level review status data is available in the manually exported Reviews report from ACC, but it is not exposed through the Data Connector, forcing users to rely on manual exports and it's not an good practice. Show More

Ability to export the model coordination module's clash matrix results (number of clashes per test) to a database, eg. .csv    We need the clash results in this format to visualise the data as progress over time, among other visualisations.   With the ability to export the results in database format a scheduler feature would be required to set this export to a regular schedule.   ACC Data Connector - the solution could be delivered through the improvement of the ACC Data Connector, which today can schedule .csv exports of clash data, however the data exported is not readable/usable... (ACC Data Connector Export):   Show More

It would be good to allow scheduling extractions in Data connector in a multiple day inside a week selection. Currently it's only on a weekly basis on a specific marked day OR on a daily basis (or every X number of days). This would be great for BIM coordination at projects that have bi-weekly meetings and would require just two updates a week, not one, but also not every single day or after two days. For example, if my coordination meetings are on Mondays and Thursdays, I want to be able to select just those two days for scheduling, which currently is not possible. Extra benefit: setting up extractions regularly that are not needed, demands server functioning that results in more consumption of energy.   Show More

The current options for extracting Activity data are "Past day" and "Custom". Custom allows use to extract a specific date range of up to 31 days to extract the Activity data. This date range does not adjust on a daily basis. Please add additional options to extract Activity data from scheduled Data Connector extractions. Show More

To give access to dashboard to project team, it could be really better to give permission by role & company. Today it's by member, 1 by 1, too long to give access to 30 people. Show More

Maybe this is burried someplace already, but I have been unable to find it. I wish there were a way for us to develop custom Project Settings within ACC. Right now, the settings barely cover basic project data (Location, Project Type, Value, Name, Job Number, etc). However, when dealing with firmwide data, metrics, and dashboarding, it would be helpful to add our own fields to this list so we can slice our PowerBI dashboards a little easier.   Some fields we would like to add for our firm would be: Client - So that we can see which clients are generating more Studio - This 'Business Unit' value in BIM360 served this purpose for us, but that was removed in ACC, so now we cannot quickly see which teams are have smooth/poor CA performances Gross Square Footage - This would be a very valuable slicer, I can track performance from our large, medium, and small projects seperately (e.g. a 4,000 sqft office project is radically different than a 400,000 sqft office project). We can also add calcuated columns and divide value by GSF to slice projects by cost per square foot. Lots we could do Thats just three for our firm, Im sure other firms would want other parameters. It would be nice if the ACC Out of the box parameter were kept light (I wouldn't want to see the OOB parameters to be a sea of junk) and firms were allowed to customize parameters for more effective, more tailored dashboarding.  Show More