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 browser and product limitations.
Beginning January 12, 2016, Microsoft stopped feature development on Internet Explorer and has been releasing only security updates. Due to inherent limitations and no further development, Internet Explorer may experience reduced performance when compared to other browsers.
A significant example is a memory leak created in Internet Explorer during navigation. Depending on the system memory, this may cause the browser to crash when enough memory has leaked. This issue is not limited to Dundas BI and is present during every navigation performed using Internet Explorer, but may surface faster with heavier implementations. To avoid this particular issue, open a new window instead of navigating to the desired URL (Ticket 66060).
Changes made in the Filter Visualizations popup may not be saved after closing Internet Explorer (Ticket 39288).
When double-clicking on a label component to edit its text, a Webpage Error (JS error) may occur in Internet Explorer. This happens under very specific circumstances but does not interfere with the work flow. Simply click elsewhere and click on the label again (Ticket 51116).
In older versions of Safari, the login fields may not be visible when accessing Dundas BI using Safari's Private Browsing mode.
Safari now has the Prevent cross-site tracking privacy option enabled by default which may cause problems loading Dundas BI when embedded and viewed in an iframe on a different domain. Users must click the Enable Application button in the iframe to access Dundas BI.
When viewing the dashboard in Re-size mode, scrollbars may randomly appear in Google Chrome. This is a known issue with the Google Chrome browser and is being investigated by the Chromium team. To remove the scroll bars, resize the dashboard (Ticket 57933).
When selecting or editing an image Source property containing a very long string, Google Chrome may freeze. This is a known issue with the Google Chrome browser and is being investigated by the Chromium team. To avoid the situation, upload the image into Dundas BI (Ticket 60230).
Using the Chrome browser, holding the Shift key prior to dragging elements will not work (Ticket 71320). This is a known issue with the Google Chrome browser that can be avoided by holding Shift after pressing the mouse button while dragging rather than before.
Pie charts with multiple slices sharing the same color may appear with gradient artifacts, especially when displaying multiple levels (Ticket 76384). This is a known issue in the Google Chrome browser as of version 69. Until fixed, avoid it by upgrading to Dundas BI 6 or later, or by disabling the GPU rasterization experimental feature in Chrome by navigating to: chrome://flags/#enable-gpu-rasterization
Embedding Dundas BI as a HTTP site in a cross-domain environment is not supported due to the changes in Google Chrome (Ticket 83769). To use an embedded instance of Dundas BI in a different domain ensure that your site can run on HTTPS.
|Firefox||When viewing a scaled dashboard in Firefox and clicking a drop down list, the drop down menu may be incorrectly positioned. This is due to a Firefox bug (Ticket 50600).|
|Edge/Internet Explorer||Table visualizations displaying many tens of thousands of rows or more may not scroll to the correct position.|
3. General / Application
|logon||If you have multiple instances of Dundas BI running on the same server, and the paths to these instances differ only by the port number, users will be logged out automatically when they navigate from one instance to another instance and log on. Returning to the previous instance requires the user to log on again.||41499|
|logon, 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|
4. 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, JDBC||
A 64-bit version of the ODBC driver is needed to work with Dundas BI's 64-bit application pool.
Discovery of table and view definitions may not work for some ODBC and JDBC 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 and JDBC 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|
|warehouse storage||The floating point values NaN and Infinity are not supported and will cause the data warehouse build to fail.||53933|
|hierarchies, in-memory storage||Previewing a hierarchy in the Hierarchy editor 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, dynamic hierarchies, period over period||Period over period cannot be used with a dynamic hierarchy.||50824|
|metric sets, period over period||Period over period cannot be added to an existing period over period measure.||50927|
|metric sets||Oracle Character Large Object (CLOB) data used with a parameter compares only the first 2000 characters. This may cause extra rows to be returned.||41741|
|expand and collapse members||The expand and collapse members functionality is not supported in formula visualizations/formula metric sets.||49485|
|data connectors, SSAS||Executing certain valid MDX in SSAS 2012 fails with Internal error: An unexpected error occurred (file 'mdmisc.cpp', line 945, function 'MDBulkSetScaIter::Start'). Try installing SQL Server 2012 SP2 to fix this issue.||50521|
|data cubes, warehouse storage||Strings longer than 900 characters (or unlimited length) cannot be indexed, which may cause performance issues when used in a data warehouse. Change the data type to a shorter set length to avoid this issue.||53199|
|Excel export, OLAP||Exporting to Excel with the measure format set to OLAP will not include the number formatting.||63034|
|data connectors, Microsoft Dynamics CRM||Some entities in Microsoft Dynamics CRM are not supported, which may result in an Internal Server Error on the RetrieveMultiple method and prevent certain tables from working.||63329|
|data connectors, Access and DBF||The Microsoft driver used to connect to DBF files does not support FoxPro dBase 3.5. As an alternative, you can use an ODBC data connector to connect to the same files.||66067|
|OLAP, metric sets||In cases where Dundas BI does the aggregating, you may need to change the aggregator from Provider to a specific alternative to avoid missing values when the measure comes from an OLAP cube. For example: when a formula is added based on the measure and the Collapse All option is used on a hierarchy.||67000|
|data connectors, SSAS, OLAP||The DRILLTHROUGH statement and other MDX queries that do not return a cellset are not supported.||69064|
5. 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) are not supported for charts appearing in a scorecard or report.||39215|
|dashboards||Drag-and-drop of files onto the dashboard canvas from outside the browser does not work in certain situations in Windows 8.||42075|
|dashboards||Positioning items outside of the canvas and moving them in through script is not supported. Consider using layers or the hidden property instead.|
|dashboards, interactions||When setting up a data input interaction, writing to a data input transform in an inherited data cube is not supported and will not be available as a selection.||62144|
|Excel export, table||When exporting columns using Group Text, the first grouped column's group header settings are applied in Excel.||73198|
6. Data Visualizations
|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 because a table does not support chart-specific styles, for example. To get the original visualization and its styling back when viewing, reopen the file or use the Revert To Original re-visualize option. When editing, use undo in the toolbar, or first check in the file, use the Update button on the Data Analysis Panel, or save a style.||42018|
|table||When the row header mode is changed to Single Indented Column in a table visualization, totals are required and will be enabled automatically on the metric set.||49787|
|table||When using the properties Freeze Total Rows and Show Totals At Bottom together in a table visualization, the subtotal row has to be loaded to display in the freeze row. If the subtotal row is too far down the table, data for it will not be retrieved and the freeze row will not be displayed.||57648|