@ihayesjr We're specifically having this problem with .mer files, but it's not necessarily isolated to .mer files. The issue with how Vault handles the checksum is that it impossible to know that the new version wasn't uploaded until we notice later that there's been data loss. This is a real risk for organizations that have adopted Vault. I'm sure virtually all organizations would prefer to host unnecessary data rather than risk data loss at an unknown time.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | New Job Type to Clear Property Values on State Change | 0 | 4.76 | 22-10-2026 |
| 2 | Re: Saving IAM only, no Multi-file popup is needed | 0 | 9.85 | 22-10-2026 |
| 3 | Provide Autodesk Job Type to Write State Change Timestamp and User to Properties | 0 | 4.23 | 22-10-2026 |
| 4 | Re: New drawing vs. "Open drawing from vault" | 0 | 5.23 | 22-10-2026 |
| 5 | Autodesk Desktop Connector file update/upload errors | 0 | 15.2 | 05-08-2026 |
| 6 | Vault Check In Blank | 0 | 5.98 | 15-10-2026 |
| 7 | Bulk Export of Markup PDFs by Review Package in Autodesk Construction Cloud (ACC) | 0 | 5.53 | 14-10-2026 |
| 8 | Why is Autodesk Login Security so strict? | 0 | 7.13 | 23-06-2026 |
| 9 | Synchronize Properties on the Client After a Lifecycle State Change | 0 | 4.76 | 22-10-2026 |
| 10 | Delay in Publishing Plugin Updates on the Autodesk App Store | 0 | 3.84 | 11-08-2026 |