Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Please allow the revit template to hold predefined worksets. We use worksets in 100% of our projects and everytime we have to recreate them manualy (we don like the method to create project with worksets and use/copy that as it is prone for mistakes)
Thanks for your submission and votes on this idea! We are evaluating where this request falls into our roadmap and will provide an update when we have made a decision.
The ability to include worksets in project templates would be great!
Even if Revit cannot have worksets in an .RTE template file; could it be made it easier to create the same worksets in each new project? My projects typically have mostly the same worksets in most projects.
Perhaps add a workset template that can be applied to a project like a view template is applied to a view.
ie: I create a new .RVT project file from my project template, and then click "Create Worksets from WS-Template" (or whatever) which presents me with a list of possible worksets -- a list that I created previously and included in my .RTE file -- and I choose the ones I want to create in this new project file.
We have all of our projects based on Workshared environment and I know the pain of creating workset manually each time when we have project setup. I have workaround that might be helpful for now until Revit development team will implement worksets as part of RTE file.
Create a new project based on your company standard template, create all required worksets in this file and save it as CENTRAL file (eg: Master_Template_Central.rvt). While you are about to setup a new project, use OPEN, locate Master_Template_Central.rvt and use "Detach from Central" and then use "Detach and Preserve worksets". Now you have got brand new file with your company standards worksets.
Most likely someone will not do this correctly and start syncing back to your "template" file. So you should keep backups. Another slightly different take is to make that file with eTransmit so that it is a transmitted file. Then user only needs to copy/paste to project folder and open to save as a central model in the new location. This would eliminate the possibility of user accidentally syncing to the template.
For now I am going with the new Dynamo player and the suggestion from rb above to avoid users making mistakes using Dhanjeetsah suggestion. Still have to manually create the central though, so it is halfway there.
Hi michael_coffey, if user uses "Detach from central", it creates a separate instance and will not have SYNC option until user saves this new file to a new location. I do not see user will make "mistake" about this until user do not understand difference between "Detach from Central" and "Create New local". If user cannot follow this simple step, he should be instructed. Since we all know Revit is event driven program and a simple push button can sometime change lots in design.
Having said that I am not ruling out the IDEA that workset should be part of a Template.
Until revit 2012 it was possible to do that, but Autodesk have canceled this function because it can generate corrupted central file. We have this answer from Autodesk after a health care of our central file. You can prepare an empty central file with your most used workset.
We've completed our review of this idea. After investigating the effort required to implement this request, we unable to add it to our roadmap at this time due to other priorities. However, we think this is a great idea so we will reconsider it as we made adjustments to our roadmap in the future. Thanks for the submission and keep voting!
While I was hoping for a different answer, it is good to actually know where the factory is heading. This way I can focus on on setting up a dynamo routine (or similar) for creating worksets, and know that I'm not wasting time in that effort. As can also confidently recommend the process to my Revit students and clients that they to do the same.
Maybe a workset placeholder would be good. We currently use a Central File instead of a template for the reason of retaining worksets. Most which need to be deleted for each project (using dynamo)
I agree but I would suggest using a view versus a sheet. In MEP we have lots of worksets to control filtering and views. If I had "active workset" parameter in the view properties it would avoid object getting place on the wrong workset. (dont forget the "none" setting) You would open a view for sheetmetal and the objects you added would already be placed with the "sheetmetal" workset. Of course it would also have to be controlled in the view template, and never check out the entire workset while in the view, unless using the workset manager to check it out.
I would also like the workset widget to show the current selections workset, like layer properties in autocad. Switching workset using the widget would change the properties of the selection to the correct workset.
This possible in Dynamo. Since this is not on the "Roadmap" Autodesk should at least create the graph as a sample file and include with the installation. Then map dynamo player to it for use by all as the 412 votes indicated it is highly needed. This would be a better appreciated attempt than just saying "we unable to add it to our roadmap".
worksets are an archaic (AutoCAD approach) to managing content within your model.
users are required to set their active workset (layer) and if not done correctly will cause issues with your views not displaying correctly.
depending on how many worksets are required within your model, may I suggest using filters and view templates to manage your content by categories visibility graphics in your Filters and View Templates.
Use Worksets sparingly if necessary at all
Linked files- a workset for each linked model
if you have a large building sort out the building areas by workset.
Stopped using an actual .rta a long time ago because you were not able to set work sets and other thing in it.
Our workaround was pretty simple, Start a project from a template. Create work sets. Save that project as companytemplate.rvt. Now every time i start a new project. I just open/detach that Revit file and save as project to new project folder. I no longer have to recreate those view templates. With the exception when a new version of Revit comes out. So at least once a year I will recreate the companytemplate.rvt.
Not a perfect solution, but works pretty well.
Just realized that another posted same idea above. great minds think alike @ Dhanjeetsah
