Filter datasource based on gridview selection

Question

0.00/5 (No votes)

See more:

I have a web page built with asp.net VB. The database is one with family members. There are three databound controls; gridview and 2 detailsview. They are working except for one details view which is bound to a datasource using a filter. I want to display information in the first detailsview of the selection from the datagrid view. This works OK. I want the second detailsview to display the parent information for the selection in the gridview. The parent and child are in the same table. The parent ID is in a field that is not a key. I coded the datasource from an example, but the detailsview displays the information for the selected row, not the parent. I can change the code to set the filterexpression to ID=4, for example and the details view displays the information for row 4.
I believe that I don't have the FilterParameter parameter properly set. What do I use as the PropertyName= in the parameter to get the value from the selected row parentid field? Using SelectedValue returns the gridview ID column which is the key.

<asp:SqlDataSource ID="SqlDataSource4" runat="server" 
        SelectCommand="SELECT ID, Last_Name, First_Name FROM contacts"
        FilterExpression="ID='{0}'" 
         ConnectionString="<%$ ConnectionStrings:mystrainfamilyConnectionString %>"
        ProviderName="<%$ ConnectionStrings:mystrainfamilyConnectionString.ProviderName %>" >    
            <FilterParameters>
                <asp:ControlParameter Name="ID" ControlID="GridView1" DefaultValue="1"  
                    PropertyName="SelectedValue" />
            </FilterParameters>
    </asp:SqlDataSource>

What I have tried:

I have found nothing that explains the proper PropertyName for the filter parameter.

Posted 6-Jul-18 5:12am

BobbyStrain

Updated 6-Jul-18 18:20pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Vincent Maverick Durano · Accepted Answer · 2018-07-06T18:21:00

Hi,

I haven't really used Wizard DataSources for complex scenarios, so I can't really give a straight solution to what you are having now.

If I were you I would use the ADO.NET way with DataSets/DataTable. Wizard DataSource such as SqlDataSource are good, but for me I would prefer using DataSets with SqlCommands - I called it the hard-coded dataset because I can write my own logic there and do stuff like Sorting and Filtering. SqlDataSource is good and could be preferred if a simple query is to be generated. But it tends to get complicated and confusing when it comes to intertwined/complex queries (just like what you are having now). SqlDataSource is also hard to maintain in case of huge blocks of code and we have to generate umpteen DataSources for different data controls. Where as in the case of hard-coded sql databind, we can reuse the code without any hiccups changing the basic query here and there according to requirements and It is also a lot easier to maintain it.

If you are not comfortable working with Sql queries, you could also use an ORM such as LINQ to SQL or Entity Framework as your data source for your data controls.

Just my $0.2.