Currently a user is forced to modify all instances in a family table when a column is added during the creation of a new instance.
Example:
A generic has four feature. Two of the features are columns of the table
The user adds a new instance and will add a third feature to the table and modify that feature for the new instance
All existing instances are the same value as the generic.
This forces all instances to be verified and tagged as modified in the workspace.
Suggestion:
Provide an overide option in the event manager to allow checkin of the generic and the new instance. Leave the other instance alone.
1 Comment
