Pinned views "Cleanup" tools

Feature Requests
1

Currently, on importing any IFC/RVT/… model, a number of pinned “Views” are automatically generated. This can be very useful for well-structured models. But it presents a challenge in cases:

  • With a lot of models => each model is interpreted as a separate ifcBuilding. For each of those, default elevations, floor plan, … are generated
  • With a lot of ‘levels’ => in Revit “Levels” are not only used to separate building storeys, but also (too often) as reference planes to model geometry. This translates to the exported model with objects that are on too many different ifcBuildingStoreys.
    I know this should be fixed in the authoring software. But since we often come to the project after the initial design phases we must deal with the resulting mess in the models created by others

Both of these result in a very big amount of pinned views:

image
image350×1130 35.9 KB

And currently we don’t have the tools to clean this up in an efficient manner. I’d like to select multiple views simultaneously (preferably by selecting the parent element above). Then delete them all together.

This is probably linked to another topic about managing libraries (locations is one of them): New “Merge” tools for model libraries - Feature Requests - Qonic

2

If part of the solution is to let Qonic be smarter about which views to generate, that is of course even better than cleaning them up afterwards! But I think it still remains useful to have more/better tools for batch deletion/management of the views.

3

Thanks for the detailed description, @Johan_De_Cock . We recognise the problem with models that bring in many ifcBuildings and storeys on import, and the cleanup it causes.

The Pinned panel (formerly Saved Views) was updated in the October release, with saved product selections added next to pinned views: Qonic October Release Notes 2026 . Batch selecting and deleting pinned views is not available yet.

We are tracking it internally, together with the question of generating fewer default views on import. The model library merge tools you described in New "Merge" tools for model libraries are related and we are keeping them in the same discussion.