I am hoping someone can help - I have reviewed the problem for days now and there's no easy way of doing this.
I can not find any way to change a configuration variable to amend how Microstation is behaving. Every time I Make Direct Attachment with a file that has overrides set, on completing the attachment, the overrides always revert back to the Reference file’s override settings set in the Original/Source file. Incidentally, when the file is referenced in as the nested attachment, the levels display fine. It is only when I Make Direct attachment that they disappear and revert back.
I have played with various configuration variables:
MS_LEVEL_EDIT_ATTRIBUTE_LIST
MS_LEVEL_SYNC_ATTRIBUTE_LIST
MS_REF_REATTACH_LEVEL_SYNC_ATTRIBUTE_LIST
MS_LEVEL_AUTO_SYNC_ATTRIBUTE_LIST
None of the changes I make seem to work. I have tried both using settings offline and through the workspace set up by the company. It seems this setting is a default and there is no easy of way of managing this task. The issue has been raised by other members various times and the only way of managing this is by copying levels out and pasting back in to the direct attachment - or using a .csv export out to then reimport back.
I have also reviewed many posts relating to these CVG VARS and none go into detail about Direct Attaching and their Overrides. Has this been resolved in Connect? I am using Microstation V8i SS3/Aecosim V8i SS6.
Anyone?
Richard,
Here is a simple test case based on the attached video clip, OpenBuildings Designer, CONNECT Edition, Update 5.
1. "ArchitecturalElements.dgn" file references "StructuralElements.dgn"
2.Level display and overrides are applied for the reference "StructuralElements.dgn"
3."LevelOverrides in DirectAttachment.dgn" file references "ArchitecturalElements.dgn" file, with Live Nesting enabled.
4. From the references dialog, "StructuralElements.dgn" file is made as direct attachment to "LevelOverrides in DirectAttachment.dgn".
5. Level display and overrides of "StructuralElements.dgn" files is retained as it was modified in the "ArchitecturalElements.dgn".
Have I not understood your problem correctly, please let me know.
Best Regards,
Raguram.
Hi Raguram,
So this is similar to the workflow I was trying to describe. The only difference in my case was that I applied overrides in the nested attachment after it was attached (allow level edit within nested references was turned on obvs).
Regardless, in either of those situations (mine and the one you demonstrate in the video), I am not able to retain overrides. If I apply the overrides before or after, once the direct attachment is made, the overrides are lost and symbology reverts back to the settings in the source file. I think this could be tested quite easily using V8i.
As you can demonstrate this is possible, I am guessing then this has been addressed in the build in CONNECT? I see you are using CONNECT Edition.
Can Bentley confirm?
Regards,
Richard
hi Richard,
I tested your workflow by making the changes in the nested references.
I noticed the reference level overrides are maintained even after making it as a direct attachment.
Yes, I am using CONNECT Edition.
I trust our support team would update you, responding to your Service Request.
RJ.