[Solved] Native Blazor Report Viewer AI Insights and Search Window appearing and won't go away

[Glenn]

I have been doing everything in my power to get the AI consent window and the search window to NOT appear automatically when using the Native Blazor Report Viewer, and the ONLY solution that I've found is to use the Telerik Control Panel to install the latest version, find the report template html file, remove the components, and then force the report viewer to use that template in the TemplateUrl parameter. The only issue though, is EVERY time you upgrade your Telerik.Reporting and ReportViewer and such, you have to do that every time, and it's quite a pain. Is there really no other way to disable these with the automatic template? The search and AI windows don't even work anyways (I don't have them linked to anything nor can I find out how). You press the X button in the top right of the windows and they don't even close. Anyone have any ideas?

ReportViewerComponent.razor:

        <ReportViewer @key="ReportKey"
                      ViewerId="rv1"
                      ServiceUrl="/api/reports"
                      PersistSession="false"
                      KeepClientAlive="false"
                      ReportSource="@(new ReportSourceOptions { Report = ReportName, Parameters = ReportParameters })"
                      Parameters="@(new ParametersOptions
                                  {
                                      Editors = new EditorsOptions
                                      {
                                          MultiSelect = EditorType.ComboBox,
                                          SingleSelect = EditorType.ComboBox
                                      }
                                  })"
                      ScaleMode="@(ScaleMode.Specific)"
                      Scale="1.0"
                      PageMode="@(PageMode.SinglePage)" />

[Dimitar]

Hello Glenn,

Thank you for the shared code and the additional information!

The described behavior is unexpected. However, I have seen it happen when an old version of the Kendo themes is referenced in the application.

Do you load the theme shipped with the NuGet packages, or do you use CDN, or another approach for loading themes? For example, in our demos, we load the default Kendo theme from the package:

    <link rel="stylesheet" href="https://unpkg.com/@@progress/kendo-theme-utils@10.0.1/dist/all.css" />
    <link rel="stylesheet" id="TelerikThemeLink"
        href="_content/Telerik.UI.for.Blazor/css/kendo-theme-default/all.css" />

    <link href="_content/Telerik.UI.for.Blazor/css/kendo-font-icons/font-icons.css" rel="stylesheet" />
    <link href="_content/Telerik.ReportViewer.BlazorNative/css/reporting-blazor-viewer.css" rel="stylesheet" />

The demo projects that I am referring to are in the installation folder of the product. For example - C:\Program Files (x86)\Progress\Telerik Reporting 2026 Q2\Examples\CSharp.

If you open the CSharp.BlazorNativeExample.VS2022/sln solution, and start any of the projects there, do you observe the same behavior? If not, it should confirm that the issue is specific to your project, and in that case, please do investigate what version of the theme is being loaded. For the latest version of Reporting, please try loading version 12.3.0 of the Kendo themes.

Regarding the AI Insights feature itself, please refer to the Telerik Reporting AI-Powered Insights Overview - Telerik Reporting article if you are interested in learning more about it and enabling it for your application after the issue above has been resolved.

If further assistance with resolving the issue is required, please send a runnable copy of the project so that I can run it and investigate the problem locally.

I hope that the provided information will help remove the unwanted behavior!

Regards,
Dimitar
Progress Telerik

[Glenn]

Hello Dimitar,

Thank you for the reply! I see what you mean with this information. I do not have the examples installed, but I think I may know the issue and you may be able to understand as well and be on the same page with me of testing the examples may not be helpful. Here is the <head> attribute of my App.razor file:

<head>
    <meta charset="utf-8"/>
    <meta name="viewport" content="width=device-width, initial-scale=1.0, viewport-fit=cover"/>
    <base href="/"/>
    <ResourcePreloader/>
    
    <!-- Telerik UI for Blazor theme & icons (version-aligned via static web assets) -->
    <!-- Using _content paths avoids CDN version mismatches with your installed UI for Blazor package. -->

    <link rel="stylesheet" href="_content/Telerik.UI.for.Blazor/css/kendo-font-icons/font-icons.css" />
    
    <!-- Your site styles load AFTER the Kendo theme to avoid overriding base component styling -->
    <link rel="stylesheet" href="@Assets["/styles/company-light.css"]" />
    <link rel="stylesheet" href="@Assets["/styles/company-hero.css"]" />
    <link rel="stylesheet" href="@Assets["/styles/company-colors.css"]" />
    <link rel="stylesheet" href="@Assets["/styles/company-effects.css"]" />
    <link rel="stylesheet" href="@Assets["/styles/company-card.css"]" />
    <link rel="stylesheet" href="@Assets["/fontawesome/css/all.min.css"]" />
    <link rel="stylesheet" href="@Assets["/styles/app.css"]" />
    <link rel="stylesheet" href="@Assets["company.styles.css"]" />
    
    <!-- jQuery is required by the Telerik HTML5 Report Viewer used under the Blazor wrapper -->
    <script src="https://ajax.googleapis.com/ajax/libs/jquery/3.7.1/jquery.min.js"></script>

    <!-- REST resources served by YOUR Reports service (keep global) -->
    <script src="@Assets["/api/reports/resources/js/telerikReportViewer"]"></script>
    
    <!-- Telerik Blazor interops (ReportViewer global) -->
    <script src="_content/Telerik.ReportViewer.Blazor/interop.js"></script>
    
    <!-- UI for Blazor interop (version-aligned via static web assets); keep defer -->
    <script src="_content/Telerik.UI.for.Blazor/js/telerik-blazor.js" defer></script>
    
    <!-- Fonts (optional) -->
    <link href="https://fonts.googleapis.com/css?family=Roboto:400,500&display=swap" rel="stylesheet" />
    
    <!-- Favicon -->
    <link rel="icon" type="image/png" href="@Assets["/icons/mmh-logo-suite/stacked-vertical/color/companylogo.png"]" />
    
    <ImportMap/>
    <HeadOutlet @rendermode="new InteractiveServerRenderMode(prerender: false)" />
    
    <title>PORTAL</title>
</head>

We are using Telerik ThemeBuilder for our css and styling, which is the "company-light.css" style you can see in the list of <link>'s. I am under the assumption that ThemeBuilder does not fully support TelerikReporting? If that is the case, for every instance of the ReportViewer do I need to somehow separately load the CDN package instead of the ThemeBuilder styles? The ReportViewer is usually rendered inside of other components on the page that are already rendered with the ThemeBuilder css package. I may be missing something here.

[Dimitar]

Thank you for sharing the code!

Judging by the code, it seems that you are actually using the Blazor Wrapper Report Viewer instead of the Native Blazor Report Viewer component.

The non-native Blazor report viewer is a wrapper of the HTML5 Report Viewer, and it does support ThemeBuilder, so its wrappers also support it(the Native Blazor Report Viewer does as well) - Telerik Reporting Displaying Reports Web Application Styling with ThemeBuilder Styling HTML5-Based Viewers - Telerik Reporting.

Did you create your custom theme from scratch, or did you use any of the Kendo themes as a starting point? If it were the latter, what was the version of the Kendo theme? If you are using the latest version of Telerik Reporting, it would be recommended to use a theme created from Q4 2025:

If you create a theme from that version, does it hide the dialogs as expected?

You could manually hide the AI prompt and search dialogs via CSS, as their container classes are .trv-ai-prompt-dialog and .trv-search-dialog, using the display CSS property.

In order to be able to assist you with the issue further, I would need you to send me a copy of the theme so that I can test it locally and confirm that the required CSS rules are missing from it.

With that being said, a complete and runnable project with the problem would be even better, as if the issue is not related to the theme, I will be able to continue investigating the other parts as well.