StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1897219
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-12-13T18:11:57.060
FavoriteCount
0
LastActivityDate
2009-12-13T18:11:57.060
LastEditDate
LastEditorUserId
0
OwnerUserId
192572
ParentId
1890939
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
The short answer: Yes. The ReportViewer can behave in the manner you describe. (Your colleague is incorrect.) There are a couple approaches for displaying all rows in your data source rather than just the first one. I'm most familiar with the List Control approach which is described here but there is also a Master-Detail approach using either subreports or nested data regions. Strictly speaking, this question is about displaying multiple data rows, not custom object collections. You might want to edit the question title from, “.NET ReportViewer capabilities: Binding to custom object collections?” to say “.NET ReportViewer capabilities: Displaying multiple rows”? When designing your report, if you place a field from your data source onto the report designer and display the report, you've noticed only one row is displayed rather than the whole dataset. On closer inspection, the ReportDesigner wrapped the aggregate function First() around your data field. This is the default behavior for the ReportViewer. What you want to do is use the List control and place your data field control(s) within it. Now, all field rows will be displayed. It is that easy. The List is a critical component in successful use of the ReportViewer. Read up on it. The List can accommodate greater complexity using its Group Expression capabilities and also by nesting List/Table controls within it. Resources: As mentioned in another post, one of the best web resources for the ReportViewer is the <a href="http://www.gotreportviewer.com" rel="nofollow noreferrer">GotReportViewer</a> site. There you'll find more info on using List, Master-Detail and more. Good luck.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PO.NET ReportViewer capabilities: Displaying multiple rows
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USEd Lee
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PO.NET ReportViewer capabilities: Displaying multiple rows
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.