Gridview ID problem

Wheeler, Lee 0 Reputation points


I have two gridviews set up. Both of them use the default scrolling buttons. In one gridview if you look at the properties of the scroll > buttons the ID property is missing like this:

<input type="image" src="..\Images_Net\Next.gif" alt=">" onclick="javascript:__doPostBack('grdList','Page$Next');return false;" style="border-width:0px;">

In another gridview on another page the same scroll button has these properties:

<input type="image" id="grdList_ctl01" src="..\Images_Net\Next.gif" alt=">" onclick="javascript:__doPostBack('grdList','Page$Next');return false;" style="border-width:0px;">

Notice the second one has the ID property. How can I make the other gridview have the ID property for its arrows? I have tried setting the clientIDMode to static and that didnt do anything. Thank you for any help!


A set of technologies in the .NET Framework for building web applications and XML web services.
3,362 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Lan Huang-MSFT 27,721 Reputation points Microsoft Vendor

    Hi @Wheeler, Lee,

    Unfortunately, I tried running your code (HAS the IDs for the navigation arrows), and no IDs were generated. Based on my test, scrolling buttons should not be able to automatically generate IDs.

    How can I make the other gridview have the ID property for its arrows?

    Maybe you could try adding the ID using jquery.

     <script src="Scripts/jquery-3.4.1.min.js"></script>
     <script type="text/javascript">
        $(document).ready(function () {
            $("#grdList :input[type='image']").each(function (i) {
                var id = "grdList_ctl0" + i;
                $(this).attr("id", id);

    User's image Best regards,
    Lan Huang

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  2. EngCream 0 Reputation points


    It seems like the issue you're facing with the missing ID property on the scroll buttons of your gridview might be related to how the control is being rendered or how the properties are being managed at the code level.

    Since setting the ClientIDMode to Static didn't resolve the issue, here are a few steps you could try:

    1. Check GridView Settings: Ensure that the settings in both GridView controls are consistent, especially regarding how they handle IDs and client scripts. There could be a property or setting that's different between the two.
    2. Explicitly Set the ID in Code-Behind: If the ID is not automatically being assigned, you might consider manually setting it through the code-behind during events like RowCreated or RowDataBound. For example:
         protected void GridView1_RowCreated(object sender, GridViewRowEventArgs e)
             if (e.Row.RowType == DataControlRowType.Pager)
                 // Find the control and set the ID
                 var imgButton = e.Row.FindControl("YourImageButtonID") as ImageButton;
                 if (imgButton != null)
                     imgButton.ID = "grdList_ctl01";
    3. Examine Page Lifecycle: There could be differences in how and when the IDs are being assigned during the page lifecycle. Check if there's any custom logic that might be interfering with the ID assignment in your gridviews.
    4. Inspect Master Page or Themes: If your application uses master pages or themes, these could affect the rendering of controls. Ensure that there are no conflicts or overrides happening that might affect one GridView differently from another.
    5. Update and Compare ASPX Markup: Ensure that the ASPX markup for both GridViews is consistent and look for any discrepancies. Sometimes, small differences in markup can lead to different behaviors.
    6. Review ASP.NET Version and Configuration: Differences in ASP.NET versions or web.config settings can affect rendering. Make sure both pages are running under the same configuration and framework version.

    If these steps don't help, you might need to look deeper into the custom scripts or library versions being used in your project, as these could also impact how client-side properties like IDs are handled.