Retaining XREF Overrides of A Nested XREF When Overlaying Into Another Drawing

[Anonymous]

Hello everyone!

I tried searching for a solution for the following issue, but wasn't able to find one, and was wondering if anyone familiar with this problems knows how to resolve it:

I have multiple source drawings - many of which where I am not allowed to modify the layer properties in those files. As of a result, I had decided to nest the source drawings into a newly created file, and modified all of the layer properties to only show what is necessary for a given discipline, which results in numerous XREF overrides for that one drawing. 

So, now when I XREF that newly created file into another, the layer properties with VISRETAIN set to 0 causes the layer properties to mimic the original source files instead of the modified layer properties I had in the nested file, which was extremely unfortunate. And since then, I haven't been able to get this to work in my favor. 

So, I was wondering - would anyone know of a way for XREF overrides to carry over from the nested XREF? I know of Layer states, VISRETAIN, and the manual approach to go about this each time I reference in the nested drawing, but that's far from productive - especially if the current project permits only one sheet per drawing file.

I had a similar issue but in regards to the creation of new layers in XREFs, and someone suggested that I create a copy of each source file, and modify the properties in that copied file and reference all of the source drawings that way, but while that would be helpful, I was trying to look for an alternative approach like the one I discussed above.

Thank you for taking the time out to respond, and I greatly appreciate each and every one of your answers!

[natasha.l · Accepted solution]

Hello @Anonymous, 

I understand what you are trying to accomplish. My recommendation is to try a different workflow, because xrefs will reference the original drawing after changes are made I would create your own copy of the xref. 

1. Open the original XREF 
2. "Save As" a different name like "XREF NAME_Edited"  
3. Use this edited file instead as your version of the org. xref

Updated: I see you mentioned that at the end of your post. I agree with this method.  

Please "Accept Solution" if a reply or replies have helped resolve the issue or answered your question, to help others in the community.

[Anonymous]

I'd like to revisit this issue as I have questions regarding the solution.  Am I understanding correctly that the solution provided is recommending that a copy of the source file be copied to a secondary file and to make whatever layer edits necessary, ie: change layer colors, turn layers on off, etc in that file?  This fix seems like one that can have costly repercussions.  What happens when the original source file changes geometrically?  Layers added, etc?  Is the newly created "XREF" master file to be overwritten with new source file and all work done over again or try to salvage what you can with layer states or similar?  This seems like it would be a nightmare trying to keep track of changes in all source files that are being "copied" to a secondary source file which is being referenced into this "Master XREF" file.

I desperately need to find a workflow or method where I can create a master xref base file, make all layer, color changes and have those changes retain there settings when overlayed or attached into plan sheets.

Are there any other ideas out there how this may work without having to create a "secondary" source file that has no "dynamic" type link to original source file in case o changes?

[RobDraw]

The OP was about nested XREFs. Is that what you are referring to?

Have you used XREFs in this fashion before or are you new to them?

You really should start a new thread as this one is marked as solved.

[jose.r.zavala]

I'm running into the exact same problem as you and the OP. In my current project, my nested XRef Layer overrides are few and relatively easy to just manually re-do them in every plan, so that's what I'll do for now. But there should definitely be a system variable to retain overrides in nested X-Refs. I'm amazed there isn't.

[maggie.terry]

What is your xrefoveride system variable set to?

[BDEZINE]

Following
Noticed that when I create a view, to use in the SSM, it also looses it's override. 😕
There must be something better then changing the original file layers over and over again (aka everytime our consultant share an update).