cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Improved "Issues & Markups" Visibility for Non-Workshared Cloud Models in Autodesk Docs

Improved "Issues & Markups" Visibility for Non-Workshared Cloud Models in Autodesk Docs

We have encountered an issue in Autodesk Docs concerning "non-workshared cloud models." The thing is, the system doesn't allow us to overwrite these models when we upload them from our local server with the same name. To work around this, we've come up with a workflow where we copy these models to another folder and create versions. This approach helps us share these copied models with clients, who can then add their own "Issues & Markups" and keep them on same models.

 

The issue is that the system doesn't generate previous "Issues & Markups" on newer versions of the same models. Sometimes we get this message: "Previous markups and calibration are still updating. Check back later" and nothing happens after that. The problem especially arises on Sheets also sometimes on 3D views.

 

Accessing the "Issues & Markups" from previous versions requires us to select those versions one by one. This means we either have to manage multiple versions on different screens to compare them, or go through a convoluted process of selecting older versions to view "Issues & Markups" and then hit the compare button.

 

This issue is causing a major headache for us, and we're looking to Autodesk for a solution. Our main request is simple: make "Issues & Markups" visible on all versions of "non-workshared cloud models."

 

I've attached a screenshot to illustrate the problem. We'd really appreciate your votes for this. Thanks.

 

Previous Version of a Non-workshared Cloud Model - Sheet View

semih_unal_0-1698171910034.png

 

Newer Version of a Non-workshared Cloud Model - Sheet View

semih_unal_5-1698176087950.png

 

Newer Version of a Non-workshared Cloud Model - 3D View

semih_unal_4-1698175942915.png

 

2 Comments
semih_unal
Enthusiast
  • Markups | Markup Promotion Improvements – Now when a file is copied into an existing lineage, markups and issues from the previous version are promoted to the new version. This feature applies to files copied manually or via a Bridge folder automation within the same project.

While this feature implemented in January has provided some improvement, I believe there's still a need for further enhancement. Based on my testing across various projects connected through Bridge, I've found that by using the new 'upload linked files' feature, uploading Revit files only by separately (for each project) can promote Issue & Markups to the newer versions.

semih_unal
Enthusiast

Please move this topic to ACC Ideas Forum.

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea