Welcome to ACC Ideas! Please note not all ideas receive a response and top voted ideas will be considered for future development. Click HERE for more information on the feedback process. Thank you for your ideas!
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
To maintain data integrity, we want to avoid project number duplication. During project setup, can we enforce a requirement for a unique project number to prevent duplication across projects? Please advise.
It’s disappointing that ACC still can’t support a basic requirement of effective document control. While ISO 19650 doesn’t explicitly forbid having multiple formats of the same content, it does require that each information container has a unique identifier agreed by the project team. In practice, most ISO 19650-aligned workflows treat different formats (e.g., native file and PDF) as representations of the same container, not entirely separate documents.
ACC, however, treats the file extension as part of the unique name, which means a document can be uploaded multiple times with the same identifier simply because it’s in a different format. As a result, the platform creates duplicates where most ISO 19650-compliant naming conventions would expect a single controlled container with multiple renditions.
This creates confusion, increases risk, and works against well-established information-management practice. It would be far more aligned with real project workflows if ACC could enforce uniqueness based on the document identifier—regardless of file extension—so that alternate formats are treated as related outputs, not separate documents.
