Skip to Content

Disable summary fields from drill down in Crystal Reports

As you know, a summary field or the group name on a group header / footer of a crystal report appear as a hyperlink. When viewing the report from Crystal Reports Designer, Crystal Reports Viewer or InfoView using DHTML /Advanced DHTML viewer, the user can click on such fields to drill down to that group. However, sometimes the user may want to disable this functionality. In a large banking corporation, the business user doesn’t want to see a new window when clicking on a sub-total field on a group header in InfoView – He’s OK to use the drill-down functionality when clicking on the group name, but not the sub-total fields. For example, a crystal report showing customers’ sales grouped by region and city in USA is displayed in Figure 1 below. The user wants to drill down to a region or city when clicking on its name, but wants nothing to happen when clicking the subtotal fields.  drill down on a group nameFigure 1. You can drill down to the detail of a group by clicking on group name or summary fields.  There’s no such property to control this behavior directly. Finally, we found out two workarounds. One workaround is quite straight-forward,by placing the fields into a Text Object. That’s, you first insert a Text Object to the group header or footer and drag the subtotal field into it. The fields will appear correctly and when clicked, no drill down will happen. This applies to all viewer types in InfoView, either ActiveX or DHTML. Another way is to use CSS, by specifyingthe CSS Class Name of the subtotal field and adding such a css class to the css file which is used by DHTML/Advanced DHTML viewer. The new CSS Class is used to prevent the subtotal field acting as a hyperlink. After some search, the way out is to change the subtotal field’s hyper link (href property) in the generated HTML page. To do this, you first specify the CSS Class Name of a field in Crystal Reports Designer as displayed in Figure2:  
You must be Logged on to comment or reply to a post.
  • I suspect the 1st option is the way to go. In the 2nd option, as soon as you upgrade your install, the solution will have to be recreated – if you remember how you did it… and if you don’t work there anymore, anyone followinf you will more than likely be quite baffled(?).
    • When the server is re-installed or upgraded, the user needs update the default.css – this can be added to the customer’s install guide 🙂
      The 1st option is more straight-forward, while the 2nd is more interesting – you can do more by specifying different CSS classes to different fields in a report!


  • Remember in the bad old days of Seagate Enterprise when the ability to supress or view headers and totals, and to build filters on reports were built into the client report viewer?