iTwin Ideas Portal (iT-3 & 5)

Currently, our ability to configure form display names is quite limited. This is an issue as the form display name is what is sent to users as an email notification. For one thing, The Display Name Property only allows us to choose from one field ...

For someone who needs to sync multiple models and group them in the same container within iTwin, we must attach all the models in one DGN file. This creates two issues: Managing multiple 3D models locally can be difficult. iTwin can’t sync DGN fil...

At present we have an option to hide clashes that has been manually or rule based suppressed from the list of clashes that still need to be addressed. It will be very useful to be able to invert/toggle these suppressed clashes so that they can be ...

Please add user access to specific models instead of the whole model. For example: If we create a coordination model which will run every day, we don't want to share these with the client. So it wood be great if we can choose which Named version t...

Possibility to combine specific metadata credentials while searching for a 3D model objects using single filter with an AND operator (i.e. "Uniclass = XXXX" AND "Element Class = XXXX") or via the use of 2no Data Visualisations at the same time.

I consider this more a bug fix than a feature request, but I digress. Currently, Issue forms shown in the iModel viewer have a comment functionality, but no ability to mention ("@") a user. This functionality is commonly used and expected in forms...

Would be really great if we could use the connectors from Flow to connect the objects of the models to data. (eg. Connect data to an object or group of objects using a sharpoint list using Microsoft Flow)

Viewing animated objects in iTwin would greater facilitate design reviews. Presently, vehicle movement - animated in Microstation - cannot be viewed (or clashed) using iTwin, which restricts the coordination of design with logistics.

The current synchronisation of iModels prevents the individual naming of the 4 files that make up the cadastre documentation. It is necessary, for quality reasons, to avoid that several documents share the same name, so the current synchronisation...

How about using Project Wise sets to connect models via Project Wise Design Integration. Sets would be created by Project Wise user and opened while creating connection (all models needed in iModel in 1 place)