StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11168354
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-06-23T09:25:37.963
FavoriteCount
0
LastActivityDate
2012-06-24T11:01:38.003
LastEditDate
2012-06-24T11:01:38.003
LastEditorUserId
797200
OwnerUserId
797200
ParentId
11168283
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Don't use just the ItemID as a dependency property but the item itself. The following scenario should fulfill your requirements: Assume that CItem is the type of one record in your master/detail view. In the View that hosts your master and detail controls, use a view model that exposes a <code>List<CItem></code> or if you dynamically want to add/remove items an <code>ObservableCollection<CItem></code> which you set as the binding target for the <code>ItemsSource</code> of your master list. In addition, create a dependency property "SelectedObject" of type CItem in the view model. In the master list for SelectedItem create a two way binding to that "SelectedObject" property. In the details view just also bind to properties of "SelectedObject" like <pre><code><TextBox Text="{Binding SelectedObject.MyProperty, Mode=TwoWay}" /> </code></pre> Now when the user in the master view selects a different record the SelectedObject property gets updated and due to that all detail bindings on that also will get an update. Edit: So if you need additional logic, think about using a callback funktion when the value of the dependency property ItemID changes. Use the <a href="http://msdn.microsoft.com/en-us/library/system.windows.propertymetadata.aspx" rel="nofollow">PropertyMetadata </a> with the <a href="http://msdn.microsoft.com/en-us/library/ms557327.aspx" rel="nofollow">PropertyChangedCallback constructor</a> when registering the dependency property. The callback function is called each time when the value of the dependency property changes. In this callback function you can trigger the additional logic you mentioned for loading/preparing the item for the details view.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to use two user controls as Master –Details
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTorben Schramme
UserOwnerUserId
1. USTorben Schramme
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to use two user controls as Master –Details
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COIn my case the Details Control has some additional logic to fetch the data which is not the part of the Master Record. I have added code for better understanding of the issue.
 singulars
 PostPostId
 PO
 UserUserId
 USuser1476446
2. COThanks a lot for fantastic solution. It worked.
 singulars
 PostPostId
 PO
 UserUserId
 USuser1476446

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.