Make Drafting Views Backwards Compatible

[jonswartz]

Many of our typical details are drafting views that only use text and detail items. These should be backward compatible with other versions of Revit. Right now, the workaround if a detail is drafted in a later version of Revit and needs to be used in an earlier version is to export the detail to .dwg and import it into the earlier version, which is messy.

[Anonymous]

I know it is near impossible for revit to be backwards compatible, but if you think about it, select things could be backwards compatible.  With select clients or systems, or entities dictating more and more of their digital files and formats often times the architect isn't in control of what Revit years to use.  The main idea here would be to have detail items or views be backwards compatible since there really isn't any technology upgrade in those formats.  The technology is consistent.  Right now if something is made in 2019, and I need it for a 2018 project, my options are limited to exporting to cad, image, or other round about ways to get it into 2018.  If you could have a save down for detail items or standards transfer I don't think that would be too difficult.

[lionel.kai]

Revit - save down Drafting Views

[sam.cBZ8UW]

Allow drafting views to be imported into older versions of Revit. Drafting views often have simpler families involved with fewer parameters. It seems like they should not be affected by the upgrade process as much as other model families and views. Which seems like it would be easier to down-grade drafting views into older versions of Revit.

Example

We are regularly working in two or three editions (currently '23-'25) of Revit depending on which version our client is using. While we usually keep our template in one of the older versions ('23 or '24), occasionally drafting views are drawn for a project in a newer version of Revit ('25) that would be nice to add to the template or to other projects in older versions. Usually, everything (model, detail, annotation, etc. families) in the new version ('25) project came from an upgraded template. So, it would make sense that drafting views in new project ('25) that utilize upgraded families would be able to be down-graded to the original families ('23 or '24) and imported into a project or template.