iTwin Ideas Portal
When mapping .idgn's to a master i.model there will be instances where the i.dgn will be revised over a period of time, each time with a difference revision (P01 - P02 etc). Currently the only way to capture this information within the imodel.hub is to include it within the file name, if this attribute field could be populated separately (or automatically for the ProjectWise Environment) then this wont need to be forced into the file name each time a mapping instance is require. This will also give a more seemless link between ProjectWise and the i.model hub.
Workaround for now: Add a cell to your file with a tag set and then use attribute exchange to update the cell. When you display the properties for the object in the iTwin, you will see the tag set values.
The required Projectwise file attributes have been added to the JsonProperties with in the Imodel . We need to update the Properties area with in Design review to display these Projectwise Properties . See attached images . As well once the ProjectWise properties are available we need to make them available for data visualization for users to create data visualizations with these Projectwise properties see Aha Idea link https://itwin.ideas.aha.io/ideas/IDEA-I-528
This type of information within imodel is crucial. Personally, I would like to see a similar interface to Project Insights where you can map ProjectWise Environment attributes to key ISO related placeholders like permitted use/suitability. This would provide the necessary flexibility when working with multiple environments with differing attribute naming conventions observed across different companies.