Dundas BI is a state-of-the-art business intelligence platform for data exploration, visual analytics, and creating & sharing dashboards, reports, and more.
Dundas BI data flow is flexible, as indicated by the background arrows in the figure . You don't need to create every element in the data flow and can drag and drop a spreadsheet or database table directly onto a dashboard.
SourceLink: a href="https://www.dundas.com/support/learning/documentation/analyze-data/understanding-the-dundas-bi-data-model">Dundas BI
ETL Layer & In-Memory Analytics
- Extract-Transform-Load (ETL) capability is built directly into Dundas BI. A wide variety of transforms are available to perform ETL, access machine learning and other advanced analytics with R or Python etc.
- Data cubes can also store data input through a spreadsheet-like interface or through custom forms on dashboards.
- Connect to your data live, store it as needed in our internal data warehouse for improved performance, or build it as an in-memory model to enable even faster analytical query results.
Where each tenant has their own database, but the solution provider hosts only one instance of Dundas BI. Assuming the database structure is the same across all tenants, Dundas BI allows you to display each tenant's data using a single set of dashboards and reports, for example, and reuse it across all the tenants rather than maintain a separate copy for each, by using data connector overrides.
- Reusing dashboards and reports is possible using row-level security if the data for all the tenants is stored in a single database.
- In this case, the data of each tenant will be identified by a tenant ID or a similar field and can be secured using custom attributes or security hierarchies, or provider security options like using SSAS roles impersonation if the data source is an OLAP cube.
User Security and Single Sign-On
- The most requested type of security is typically Single Sign-On (SSO).
- SSO is an authentication process that allows multiple applications to be accessed by using a single set of login credentials.
- If you have two applications, one embedded within another, it would be tedious for user to enter their user-name and password twice when they try to go into the reporting section of your application.
- SSO allows you to have user accounts and logins that are taking place in your own tool/application, which will also grant automatic access to your embedded tool
Placeholders in SQL query
A placeholder marks where in the query to insert the value from a parameter, which you can later connect to a filter or script on a dashboard or set to an attribute value.
Placeholders can also be pass into the Stored Procedure.
Each parameter is enclosed between dollar sign ($) characters.
When you want to pass a parameter value from a dashboard or view directly into one of the transforms in your data cube, bridge parameters are an optional intermediate step where you can convert or customize the parameter value.
The bridge parameter converts values from a hierarchy or another type not directly compatible with your query or transform.
The script language used in bridge parameters is DundasScript, is similar to C#.
The script receives one of the derived types of ParameterValue as the $input$ placeholder, which will correspond to the Value Type you select when creating the bridge parameter.