I have a central file called sample.rvt file. Inside this central file I have my standard workset around 30 members. Now I am creating a new central file and I need all my previous sample worksets (which is inside sample centerl file). Is this any way to import worksets one file to anther file or I have to create all worksets again.
hello, its better to link file individually into a central file easy to manage and don't use import, link them thanks
Thanks,
Please note this is two separate file or I can say two different project.
Dear,
Simplest way is to take a copy from the first project and delete all elements and refer to it as the new project. For sure this method is applicable if you are starting a new project.
Kindly if this solved your issue, mark as solution to help others.
You found a post helpful? Feel free to give it a like!
Your question got successfully answered? Click the 'Mark as Solution' button.
alt="Autodesk Expert Elite" style="width: 150px; display: block; margin-bottom: 10px;" >
Mahmoud Zeidan
BIM Manager / Mechanical Engineer
hello, i haven't try this before. my suggestion 1) open your project 2 (all user connected to project 2 "relinguish all mine and detach from project 2)
2) open project 2 and detach from central 3) link all worksets to project 2 4) make a new central of project 2. thanks
Does anyone else find it absurd that as of Revit 2017 this feature has still not been added to the "Transfer Project Standards" list? Come on Autodesk, this is a basic function your users are requesting. And more absurd, Autodesk is pointing us at a 3rd party App... Srsly?
AutoCAD All over again...
Autodesk may not add such feature ever, simply because worksets should differ from one project to another, based on several items. As per Mastering Autodesk Revit series, "When dividing your project into worksets, itās important to think about the larger building system rather than trying to isolate its individual components."
"A good way to think about dividing up worksets is to consider the building elements and the number of people working on each of these elements. A basic breakdown of a projectās components might include the following:
ā Exterior skin
ā Core
ā Interior partitions (in a larger building, by floor)
ā Site
ā Furniture, fixtures, and equipment (FF&E)
"
or may be
"
ā Exterior and Structure
ā Furniture
ā Interiors
"
or may be
ā Eastern Wing
ā Middle Wing
ā Western Wing
Or even by floor for large towers
worksets should not be used like layers in a CAD application. One of the biggest challenges facing teams is how to understand the difference between CAD layers and Worksets. Some teams typically want to try to manage worksets as they managed layers in CAD, which can result in worksets named Doors, Windows, Walls, and so on. Although this is effective management in a CAD environment, you donāt want to create all of this structure for worksets. Not only is it time consuming, but it doesnāt provide any benefit.
And it also may cause problems and inefficiency due to time lost by team members trying to acquire permissions from each other and asking each other to relinquish every 5 minutes.
@Anonymous wrote:
Autodesk may not add such feature ever, simply because worksets should differ from one project to another, based on several items. As per Mastering Autodesk Revit series, "When dividing your project into worksets, itās important to think about the larger building system rather than trying to isolate its individual components."
"A good way to think about dividing up worksets is to consider the building elements and the number of people working on each of these elements. A basic breakdown of a projectās components might include the following:
ā Exterior skin
ā Core
ā Interior partitions (in a larger building, by floor)
ā Site
ā Furniture, fixtures, and equipment (FF&E)
So, you say the worksets should differ from project to project? Totally disagree. The worksets that I use are the same from project to project. I can create all of them in less than 30 seconds.
Why did you give a list of standard worksets, if they should be different from project to project?
First of all, thank you for your reply.
Second, I did not give a list of standards worksets, I just gave examples. If you please, recheck my reply, I gave Three totally different examples.
Third, that's not even my opinion, nor my words, these are quoted. It's written in the Mastering Autodesk Revit series.
Fourth, If you have a villa or a small house with two users, and another project, with 4 or 5 users.
And maybe a Tower with many 6 or 7 users. How could the worksets not differ from one project to another.
The following are also not my words, It's quoted from Mastering Autodesk Revit series.
"How Many Worksets Do You Need?
A good rule of thumb is that you should have one or two worksets for every person working on the project (besides Shared Levels and Grids). On a small project with two or three people, you might only have three or four worksets. On larger projects, you could have a dozen or so."
Maybe you don't understand what you are quoting. Those are examples of lists of standard worksets.
There are many standard approaches to using worksets. Like I said, I use the same ones for every project.
worksets should be used in a limited fashion. regardless of how many people working on a project.
worksets are more of a crutch to help AutoCAD users migrate to Revit where they are treating a workset as a Layer.
In my opinion worksets serve a small purpose -
1) place a link on its own workset
2) a breakdown by discipline maybe.
too many worksets create issues of misuse
Filters and view templates would be a cleaner workflow.
the Author (s) of Mastering Autodesk Revit series provide suggestions, these are not hard and fast rules to follow.
there are too many options to explain because of the varying building types and uses.
keep it simple and minimize the use of worksets where it makes sense.
kadmonkee,
This thread has swung wide of the original question. I wanted to know why it was not a feature to bring Worksets from one project to another project, not a critique of our in-house practices. We use Worksets, View Templates and Filters to control both the 2D & 3D model displays for use and export, as well as Printable sheets. We control color, transparency, and which systems we would like to display. Filters to us are much like layers, so we typically only use them to control color, transparency, and if something will show up. However, we've run into issues with them as well when there are too many. The same can be said for Worksets. If we had more control of the MEP settings, say, down to the family Name under View Templates, we would just use View Templates. We work in the MEP field and simple filters and View Templates sometimes are not enough. We also have multiple designers working on the same project which sometimes necesitates the use of worksets so we are not stepping on each other's toes. This certainly does not fix all coordination issues in-house, but we have found it is a way to mitigate most coordination issues with eachother.
The question remains:
Why is the ability to transfer in-house standard Worksets not in the "Transfer Project STANDARDS" window?
Thank you all for your suggestions ideas and opinions.
Respectfully,
Darrell.
My guess is because it was designed to work with non work sharing projects, where worksets don't exist, as well. If you have standard worksets that must be using for every project, save them in a template project RVT, not a template template RTE (because RTE cannot hold worksets), then Save As each time you need to create a new project. There also is some Dynamo script yo import worksets from an Excel, if you want you go that way.
Single Transfer from JOTools can do the job you are looking for:
https://apps.autodesk.com/RVT/en/Detail/Index?id=1090472181312958476&appLang=en&os=Win64
@Anonymous wrote:Now 2020...
Brilliant! Revit 2021 is just around the corner. Do you expect something to change?
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.