Agree, just like Text Favorites, you should not have to go into all dgns and have to sync the local item type copies manually back to library.
Alternatively an option to auto sync to library would facilitate this?
You mean Item Type definitions in a DGNLib? The definition is used when a user creates an Item instance in a DGN model.
The problem is how to make that change known.
Suppose you change an existing Item Type property definition from Text to Number. If that change were to be propagated to existing uses of the Item Type, then any existing Item property that could not be converted to a number would fail.
Suppose you add a new Item Type property definition. How should existing Item instances be notified of the new property?
Suppose you delete an Item Type property definition. How should existing Item instances be notified of the new property?
You should compare Item Type definitions with other schemas, such as SQL used in relational databases. Once a schema (i.e. Item Type definition) has been published and is in use then it should not be changed. One way to handle this issue is to propose a revised version of the schema that replaces the existing schema for new use.
You mean Item Type definitions in a DGNLib? The definition is used when a user creates an Item instance in a DGN model.
The problem is how to make that change known.
Suppose you change an existing Item Type property definition from Text to Number. If that change were to be propagated to existing uses of the Item Type, then any existing Item property that could not be converted to a number would fail.
Suppose you add a new Item Type property definition. How should existing Item instances be notified of the new property?
Suppose you delete an Item Type property definition. How should existing Item instances be notified of the new property?
You should compare Item Type definitions with other schemas, such as SQL used in relational databases. Once a schema (i.e. Item Type definition) has been published and is in use then it should not be changed. One way to handle this issue is to propose a revised version of the schema that replaces the existing schema for new use.