StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18337559
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-08-20T14:25:12.917
FavoriteCount
0
LastActivityDate
2013-08-20T14:25:12.917
LastEditDate
2017-05-23T12:25:51.337
LastEditorUserId
-1
OwnerUserId
1169696
ParentId
18277553
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
Generally, the <code>Selected</code> property in <code>SelectList</code> will be totally ignored by the HTML helpers unless there's no other option. If <code>DropDownListFor</code> can find the value by other means, it will insist on using that value. In this case, it will use the value of <code>model.PersonType</code>(<code>.ToString()</code>) - but that's not what you want, judging by the <code>model.PersonType.ID</code> you pass to the <code>SelectList</code>. More info in <a href="https://stackoverflow.com/questions/17691742">the answer here</a>. Workaround One easy workaround that should work would be to set: <pre><code>ViewData["PersonType"] = model.PersonType.Id. </code></pre> The helper looks in ModelState first if it exists - i.e. on POST. This should work already, since <code>ModelState["PersonType"]</code> will be populated with the actual selected value that was posted. After ModelState it will look in <code>ViewData</code> - with <code>ViewData["PersonType"]</code> first, and only then <code>ViewData.Model.PersonType</code>. In other words, you can "override" the value on your model with a value set directly on <code>ViewData</code>. Better (IMO) solution The more general, "better practice", way to solve it (which also avoids having a custom model binder in order to translate the POST'ed ID back to <code>PersonType</code>) is to use a ViewModel instead of working with full models in your view: <ul> <li>Have a <code>PersonTypeID</code> property - instead of <code>PersonType</code>.</li> <li>Populate it with <code>PersonType.ID</code></li> <li>use this in your view <ul> <li>VB.NET: <code>Html.DropDownListFor(Function(model) model.PersonTypeID)</code>, or</li> <li>C#: <code>Html.DropDownListFor(model => model.PersonTypeID)</code></li> </ul></li> <li>When form is POST'ed, translate the ViewModel (including <code>PersonTypeID</code> => <code>PersonType</code>) back into the actual model in your POST Action.</li> </ul> This may seem like more work, but generally there tend to be many occasions in a project where you need more view-specific representations of your data to avoid too much inline Razor code - so translating from business objects to view models, while it may seem redundant and anti-DRY at times, tends to spare you of a lot of headaches.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODropDownListFor not selecting the selected item in the SelectList
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USJimmiTh
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODropDownListFor not selecting the selected item in the SelectList
 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. This table or related slice is empty.

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.