iTwin Services Ideas

Got an idea? Share it with us. See an idea you agree with? Vote and join the discussion. Want to be more involved? Please sign up for Usability Testing.

Revision and Suitability Metadata fields

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.

  • Lee Garratt
  • Aug 12 2019
  • Future consideration
iModel management / Portal
  • Adrian Crowfoot commented
    May 25, 2022 21:02

    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.

    ×

    Attachments Open full size

  • Jean-Paul Gauthier commented
    November 01, 2021 13:08

    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

    ALIGNJV_Project...
    ALIGNJV_Project...
    ALIGNJV_Project...
    ×

    Attachments Open full size

  • Matthew Howdill commented
    August 07, 2020 04:34

    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.

    ×

    Attachments Open full size

Related ideas