Legacy Ideas are now read-only and have been migrated to our new platform: Aha! Click Here

Under Review

Enhancement 922121 has been filed for this feature.

Item Types: Propagation Policy

With MicroStation CONNECT, we can attach Item Type data to a DGN element.  Those data are user-define and can be used subsequently to extract business information from a DGN model.

What happens when an element is edited?  If the element is deleted, is seems reasonable that the Item Type data should also be deleted.  But what happens if an element is split in some way: say a multi-line is dropped, or a shape is divided in two.  Should the Item Type data be copied to the components of that dropped multi-line, or applied to both halves of the divided shape?  Or, should the Item Type data be deleted?

Different usages will have different requirements.  That calls for a user-defined propagation policy for Item Type data.  That policy is analogous to the propagation policy already in place for MicroStation Named Groups.

Parents
  • There is need not to lose Items on element drop. For example Microstation imports ESRI SHP polygon collection as cell elements which is not easy to work in DGN environment. If user drops element it deletes Items without asking which is not expected.

Comment
  • There is need not to lose Items on element drop. For example Microstation imports ESRI SHP polygon collection as cell elements which is not easy to work in DGN environment. If user drops element it deletes Items without asking which is not expected.

Children
No Data