We need that the levels shown in the properties of objects work with the concepts of buildings or scope boxes, for objects that are inside those same scope boxes. Let me explain why this is a time saver for most users that design multiple buildings in the same Revit document.
We often work with projects that contain multiple individual housing buildings, with different levels to follow the terrain. Currently it is more practical to split all those buildings in different files due to the way level works today. The downside with splitting into separate files is that one needs often to sync/replicate all operations, and families in all the files. That is extremely time consuming due to system families, and loadable families not being in a live link. If those would be live, in a company cloud library, then it would be something else, also very useful.
Back to the main idea, even though we create scope boxes to limit the extents of levels, the levels shown in the properties for the objects that are inside those same scope boxes (for instance walls) are not contextual, is just a collection of all levels in the project.
It is very useful that once levels are constrained to scope boxes or a building parameter, they do not show for elements outside those scope boxes or buildings. Its pure logic, it works like that in reality. If that can be done, we can design faster.
If this real world relation is implemented we could more easily design, schedule present projects with multiple buildings without the need of having so many files, and manual work to sync the commonalities between them.
