StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17695615
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2013-07-17T09:06:57.820
FavoriteCount
0
LastActivityDate
2013-07-17T09:13:24.710
LastEditDate
2013-07-17T09:13:24.710
LastEditorUserId
1169696
OwnerUserId
1169696
ParentId
17691742
PostTypeId
2
Score
22
ViewCount
0
LastEditorDisplayName
text
Body
This tends to stump people a lot - apparently the roadmap for MVC 5 includes more intuitive DropDownList helpers. When you do: <pre><code>@Html.DropDownListFor(x => x.TimeOption ...) </code></pre> ... the HTML helper will do everything in its power not to use the value you set to <code>Selected = true</code> in your <code>SelectList</code>. It will: <ul> <li>Try to get it from <code>ModelState</code> - which it won't get on the GET request</li> <li>Try to get it from <code>ViewData</code> - which it will get, because you have a <code>TimeOption</code> property on your model.</li> </ul> Only if both of those attempts fail, will it succumb, and use what you asked it to use. So, in your case, it will use the current value of <code>TimeOption</code> on your model as the selected value. Which should be fine, because that's what you asked for in your <code>SelectList</code> anyway (<code>(int)Model.TimeOption</code>), right? Wrong. Because it will not cast your property (<code>enum</code>?) to <code>int</code> like you do. It will convert it to a string. For an <code>enum</code> that yields the enumeration's name - e.g. <code>PastMonth</code>. If <code>TimeOption</code> is a custom class of yours, it will be the result of <code>ToString()</code>. Then, when it doesn't find that string as one of your <code><select></code> values (because they're all integers), it decides not to make anything selected. In short: <code>SelectListItem.Selected</code> has no effect on the helper. If your helper call specifies a name (either literally or through a lambda expression), the helper will use anything in <code>ModelState</code> or <code>ViewData</code> with that name, and convert it to a string. In most cases this happens with enumerations. The easiest way to get around it is to use the enumeration's name, rather than its int representation, as the value for the <code>SelectListItem</code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODropDownListFor not respecting Selected property of SelectList
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJimmiTh
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 respecting Selected property of 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. COSeems like either an oversight or a weird design decision. I assigned the integer enumeration value to ViewData, and it works. Thanks for your help.
 singulars
 PostPostId
 PO
 UserUserId
 USSam

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.