Porting sheets over from another file should be an easy and obvious thing to do to reduce work and maintain consistency across projects. Instead, this feature misses the mark on so many things, falling below basic user expectations. Just google the problem and read people's perplexed reactions.
All we want is to be able to copy over sheets from another project so we can start a new project with the same size and named sheets as a previous file.
The ask is very simple:
- Allow us to copy over any sheet from another file, not just sheets without Views.
- Sheets should not have to be empty of Views to be copied over. Obviously, we just want the sheets, not the views. Allow us to see all the sheets and to copy just the sheets + sheet name. Having to go into the old file and delete all the views from the sheets in order to transfer the sheets over is absurd.
- If there's a sheet in the file you're copying into that has the same sheet number, ask if we'd like to override it and the sheet being used.
- Currently the default automated action is that it ignores that sheet and moves on. But often I don't care what's in my file already - I just want to use the sheets from the other file as a starting point. The goal is to get all the sheets consistent. Instead, I'm left with a mixed bag of sheets. I solve this by deleting all old sheets beforehand, but this can be solved with a smarter import process too.
- When there is an object with the exact same name in both files, ask if we want to have a copy made or if we want to use the host definition.
- Give us choices when there are conflicting objects with the same name. I detest when Revit makes the choice of creating duplicates of an object when it's obvious that the two objects are exactly the same. There must be a better way to detect differences between objects. We struggle enough to try and keep our files clean of useless duplicates. Having Revit contribute to this undesirable behaviour makes no sense.
Please clean this feature up. It has the potential of being very useful and integral to our workflows. Thanks.
