tag:blogger.com,1999:blog-9240097.post8914686621465191140..comments2024-03-18T12:04:13.830-07:00Comments on Revit OpEd: Revit 2015 - Closing a Workset and Linked File Ownership ConflictStevehttp://www.blogger.com/profile/14230364057800484763noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-9240097.post-27829604399427524292014-10-23T15:50:55.099-07:002014-10-23T15:50:55.099-07:00Thanks, it does seem to mitigate the issue. In the...Thanks, it does seem to mitigate the issue. In the past I've seen visibility control conflicts arise when they are assigned to different worksets. They intended them to be able to have different workset assignments per instance so we'll have to see if it helps in the long run.Stevehttps://www.blogger.com/profile/14230364057800484763noreply@blogger.comtag:blogger.com,1999:blog-9240097.post-28252487585092973492014-10-23T06:34:55.084-07:002014-10-23T06:34:55.084-07:00In the past I will place the instance for the Mode...In the past I will place the instance for the Model and place it on the linked model workset which I then take ownership of to avoid movement. I place the type for the model on workset 0 so that it allows users to be able to reload the model if they need to. Maybe this would work avoiding this issueWill Wydockhttps://www.blogger.com/profile/06630942504886800097noreply@blogger.com