Microsoft KB Archive/319225

= FIX: Changes do not propagate to duplicate predicates when you detach a role connector in an ORM source model =

Article ID: 319225

Article Last Modified on 8/12/2005

-

APPLIES TO


 * Microsoft Visio for Enterprise Architects 2002
 * Microsoft Visual Studio .NET 2002 Enterprise Architect

-



This article was previously published under Q319225



SYMPTOMS
When you detach a role connector in an Object Role Modeling (ORM) source model, the changes do not propagate visually to duplicate predicates.

For example, suppose that an association (for example, A has B) is duplicated in the graphical representation of an ORM source model. When you detach a role in the predicate from the object type of the role (for example, to reattach the role to another object type), this change is not displayed on graphical duplicates of the predicate even though this change is made internally in the model.



WORKAROUND
To work around this problem, manually change all other graphical instances of the role attachment after you change a role attachment. If the role connection is moved to a different object type that is not displayed on a page that contains a duplicate of the predicate, drag another instance of this object type onto that page from the business rules editor to display the new connection.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.



Scenario 1: Move Role Connection to New Object Type That Appears on All Relevant Pages
 Suppose that pages 1 and 2 of an ORM source model both display the following fact types:

F1: Employee has office in Building

F2: Room is in Building

 Detach the second role of F1 from Building, and then attach this role to Room to change F1 as follows:

F3: Employee has office in Room

 In page 2, notice that the duplicate of F1 appears unchanged, even though the change is made in the model; therefore, F1 on page 2 verbalizes as F3. To avoid confusion, make sure that the displays are consistent. To do this, manually repeat on page 2 the change that you made to page 1; that is, detach the second role of F1 from Building and then attach it to Room.

NOTE: This problem also occurs when the duplicate predicate appears on the same page as the original. However, this scenario is less common.

Scenario 2: Move Role Connection to New Object Type That Is Not Displayed on All Relevant Pages
 Suppose that page 1 of an ORM source model displays the following fact types:

F1: Employee has office in Building

F2: Room is in Building

</li> Suppose that page 2 displays a duplicate of F1 but does not display the object type Room.</li> Detach the second role of F1 from Building, and then attach this role to Room to change F1 as follows:

F3: Employee has office in Room

</li> In page 2, notice that the duplicate of F1 appears unchanged, even though the change is made in the model; therefore, F1 on page 2 verbalizes as F3.</li> To avoid confusion, make sure that the displays are consistent. To do this, drag an instance of the Room object type onto page 2 from the Business Rules window, and then manually repeat on page 2 the change that you made to page 1 (that is, detach the second role of F1 from Building and then attach it to Room).</li></ol>

Additional query words: EA

Keywords: kbbug kbpending kbvs2002sp1sweep KB319225

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.