CAD layers resetting when refreshing Linked CADs

[challstrom]

We are working with an Architect that uses AutoCAD. We link these files as background for our work. Inconvenient, but workable.

We occasionally receive an updated background from the Architect. The new file has the same name and same layer names, just revised linework. When we reload the linked CAD file, the CAD layers  found under the "Imported Categories" tab reset. This forces us to go through and turn off the entire list of unwanted layers across multiple disciplines.

They reset for views with and without templates assigned. I've made sure the CAD VISRETAIN variable to is set to 1. This happens when we "Reload From.." or "Reload" in Revit. I've tried with the "Preserve graphic overrides" both on and off.

Anyone have a thought or solution?

[RobDraw]

Are you on the cloud or a local network?

[s.borello]

Have you tried a view template?

[challstrom]

Should have mentioned, I'm running Revit 2022

@s.borello  I can set a view template, but the CAD layers still revert to visible. This happens inside a view template (if one is applied) or in the view itself (if one is not).

@RobDraw The working file is in BIM360, but I've tried both a local and BIM360 location.

Steps to recreate are as follows:

• Create a new Revit project from built-in template.
• Save it to a location.
• Link CAD file Version1 (either local or BIM360. I've tried various CAD files).
• In Revit go to Visibility/Graphics-Imported Categories and turn off some layers.
• Copy CAD file Version1 to new file Version1 (in different location to avoid naming issues).
• Replace old CAD file with new CAD file (if using the "Reload" option).
• In Revit reload (or "reload from...") CAD file.
• CAD layers in Revit revert to visible.

The problem doesn't exist if the linked file is edited, but only if replaced/reloaded.

Can anyone verify that they get the same issues?

[challstrom · Accepted solution]

For some reason, I cannot replicate the problem any more. 😲 😵 😠 It was a pain last Friday (2/25) but no longer.

I'm not sure if my we're loosing our minds, or if AutoDesk fixed something somewhere. Seriously starting to doubt my sanity, but myself and three coworkers have been battling this issue for the last 5 months.

Regardless, this issue has mysteriously evaporated. Guess I'll table this issue until it shows up again.