Dundas BI - Product Notes
The Product Notes for Dundas BI contains information about features that work differently or are currently unsupported depending on the type of data you are working with or other conditions. This includes product limitations.
2. General / Application
|login, Safari||When accessing Dundas BI using Safari browser and Private Browsing mode, the login fields will not be visible.||N/A|
|login, Windows Authentication||Regarding Windows Login/Authentication, note that Dundas BI does not support domains from separate forests for the purposes of logging on. In other words, the Dundas BI application pool user and any Windows accounts used to log on to Dundas BI must be from domains in the same forest.||51121|
|user interface||If your web browser has a plugin installed that adds a toolbar or occupies a portion of the browser real estate, this will affect the coordinate system of Dundas BI, resulting in various UI issues.||N/A|
|web browser requirements||Internet Explorer 10 is no longer supported.||N/A|
3. Data Preparation / ETL / Analysis
|data connectors||Discovery of scalar-valued functions and other non table-valued functions is not supported.||40665|
|data connectors||If you edit an existing non-relational or non-OLAP data connector, make some changes to it (e.g., via Define Structure), and then perform a re-discovery, previously discovered structures will remain under the data connector in Explore. If you then try to use these previous structures you may encounter connection errors.||41508, 50426|
|data connectors, Access||Crosstab queries and linked tables are not discovered. The crosstab queries and linked tables are available if using manual queries. Another option is to create parameterless SELECT queries to the crosstab queries or linked tables (which will be discovered as views).||50856|
|data connectors, ODBC||
Some ODBC drivers are only available in 32-bit versions. To use 32-bit drivers on a 64-bit server, you need to run IIS or your application pool in 32-bit mode.
Discovery of table and view definitions may not work for some ODBC data sources. As a workaround, use data cubes based on manual SQL query.
Discovery of table relationships (e.g., foreign keys) may not work for some ODBC data sources.
Stored procedures and functions are not discovered.
|date mapping, OLAP||If the OLAP hierarchy being mapped has a data gap, using the option to manually set the start date will yield the wrong results. Specifically, years after the gap will be incorrectly mapped.||40681|
|hierarchies, in-memory storage||Previewing a hierarchy in the Hierarchy Designer may be slow if the underlying data cube is using in-memory storage. You may get better performance by using warehouse storage for the data cube instead of in-memory.||50414|
|metric sets, OLAP||Metric set automatic count measures are not supported for OLAP.||41266|
|metric sets, dynamic hierarchies, period over period||Period over period (pop) cannot be used with a dynamic hierarchy.||50824|
|metric sets, period over period||Period over period (pop) cannot be added to an existing pop measure.||50927|
4. Dashboards / Reports / Scorecards
|filtering||The Single Number filter should only be used to filter integer data values. To filter decimal type data, use the Range Number filter instead.||39329|
|reports, scorecards||Reports and scorecards do not support metric sets with data retrieval format set to Raw Data. These are metric sets created when you drag a database table directly onto the canvas.||41089|
|reports, scorecards||Reports and scorecards do not support the Frame component.||39702|
|reports, scorecards||Zooming and scrolling (scrollbars) is not supported for charts appearing in a scorecard or report.||39215|
5. Data Visualizations
|expand and collapse members||The expand and collapse members functionality is not supported in formula visualizations/formula metric sets.||49485|
|re-visualizing||When re-visualizing a data visualization from one kind to another, only the underlying metric set is maintained and not any visualization-specific properties. This is not a limitation per se but it means that if you go to apply certain styling to a chart, re-visualize it as a table, and then re-visualize back to the same kind of chart, you may lose some of the original styling. This is because a table does not support chart-specific styles. To get back your original styling you can use general strategies such as checking things in before re-visualizing (so that you can undo checkout later, or roll back versions), using the Update button the Data Binding Panel to update the metric set's default visualization, or saving visualization properties as a style.||42018|
|table||When the row header mode is changed to Single Indented Column in a table visualization, totals will be enabled automatically. You can see this if you open the Data Binding Panel, click Edit, and then look for the Shown Totals field.||49787|