Articles in this section

How to Disable (Hide) Dashboard Parameters in Embedded Dashboards in Bold BI

Published:

You can prevent end-users from seeing or re-enabling dashboard parameters in embedded dashboards while keeping parameters available in the Bold BI portal for designers. This restriction is enforced on the server to avoid client-side tampering.

  • Applies to: Embedded dashboards only (Bold BI Embed SDK)
  • To validate, ensure you already have:
  • A published dashboard to embed
  • An application that embeds dashboards using the Bold BI Embed SDK

Configuration Steps:

Step 1. Embed the dashboard using the Bold BI Embed SDK.
  • Before embedding, keep (or add) the viewer option that disables parameters:
    image.png
Step 2. Disable dashboard parameters in the embed configuration
  • Set viewer.dashboardParameter to false in your embed configuration.
viewer: {
 dashboardParameter: false
} 

Example code placement in VS Code:

image.png

In an ASP.NET Core Bold BI embedding application, the embed configuration is defined in the client‑side JavaScript file located at:
wwwroot/js/Index.js

Step 3. Verify the embedded dashboard
  • Run the application.
  • Load the embedded dashboard in your application and verify that parameters are hidden.
Step 4. (Optional) Validate that the portal experience is unchanged.
  • Open the same dashboard in the Bold BI portal and confirm parameters are still available for design and analysis.

Behavior Comparison

Scenario Earlier Versions v15.3+
Parameter enforcement Client-side Server-side
JavaScript override Possible Not possible
Embedded dashboards Parameters could be shown Parameters always hidden
Bold BI portal Parameters available Parameters available

Example Embed SDK configuration

var embedConfig = {
 dashboardId: "<dashboard-id>",
 embedType: "dashboard",
 environment: "enterprise",
 viewer: {
   dashboardParameter: false
 }
}; 

Related Articles

Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
EO
Written by Erick Oloo Awino
Updated:
Comments (0)
Access denied
Access denied