Outstanding Izenda Issues

 Business Intelligence Bugs

"1.      We are unable to schedule an emailed dashboard..." - FIXED

Fixed in  6.10.0.3,  Scheduled BI dashboards depend upon 2 factors - 1. the Schedule must be setup on the dashboard and Saved.  2.The scheduled time must fall within the window of the scheduled process "Process Scheduled AdHoc Reports" for example - if you set up a scheduled report to run at 11:50 am, but the scheduled process is set to run every hour with a last runtime of 11:20, the report will not be sent until the next run of the scheduled process or 12:20.  Manually kicking off the Scheduled process will immediately send any reports scheduled to send earlier than the time you kick off the process. 

"2.      Scheduled Embedded reports do not export in the correct order." - FIXED

Fixed in 6.10.0.3., - February  2016.  Scheduled reports now export in order Report titles also export 

 

"3.      If multiple reports have the same filters but different values in each filter..."  - CLOSED

This is by design - Izenda applies all filters to all dashboard parts in common. So if a Dashboard has a part which has the filter Thing = x and another part where Thing = y then Dashboards will ignore these filters on the part level, and will apply the same value across parts on the dashboard level. Basically, you can't have multiple filter sets in a Dashboard - there can only be one set of filters applied from the dashboard down to the parts, and all those values must agree.

 

 "4.     Syncing between admin dataform updates and BI reports" - FIXED

This issue has been resolved with fixes applied in Release 39 of ClientSpace which refresh the server cache more frequently.  

 

"5.      Saved a dashboard schedule.  When I re-open the schedule some of the information has been overwritten. " - FIXED

Date changed from 1/26/2016  to 12/31/9999

Time changed from 9:58 am to 6:59 PM

Send Email as HTML2PDF – changed to Link (actually sent as pdf)

IZENDA RESPONSE - We've identified this issue as another case of an issue already confirmed for a fix. The fix will be released in version 6.10.0.3, on February 23, 2016.

 

 "6.      Dashboards are not filtering when open.  They require a refresh to get the correct data" - CLOSED

See item #3 - Dashboards require all included reports to have the exact same filters applied in order to automatically filter all of the reports on open.

 

"7.     When selecting a ‘User’ calculated field as a filter it will not load, the filters stay in ‘loading’ process"

Right now the only option is to use a text-entry filter for fields concatenated within the tool.

 

"8.     Column Labels and values do not respect the Justification settings under "Advanced settings" - FIXED

We've got a fix scheduled for version 6.10.0.3, which we expect to release on Feb 23.

 

"9.     Emailed Dashboards do not retain dashboard formatting and are missing report titles" - FIXED

We agree that formatting is not ideal. We will have an improvement in it available in v6.10.0.4 that includes tile Titles when added, and spaces tiles.

Fixed in 6.10.0.4  in March.

"10. Reports will not save if the reports are one unit in height, and right next to each other vertically..." - FIXED

        There is a fix for this case available with our Public Maintenance Release, 6.10.0.3. Please check our latest Maintenance Build

"11. Issue with the behavior of the Autocomplete filter (basically a type-ahead filter) - even though the "blank" checkbox is set the filter is getting included in the generated SQL when left blank, which is filtering out all the records." - FIXED

        We've reproduced the error and we think we can schedule a fix for the upcoming 6.10.0.4 release, this was released on March 22 

"12 Error:  Failed to set current report set:  xxxx (xxxx=name of dashboard) When this error occurs you have to close and reopen the report/dashboard and then the dashboard works as expected." - CLOSED

        Error seems to occur if the Application pool on the web server is recycled while a report is open.  This is due to the encoded interaction between Izenda Reporting and the way it utilizes the application pool.  This is just the way it works.

 

"13 When applying the filter “Last 30 Days” to a report to show all activity in the last 30 days, but if they add something today, it does not show on the report."  - FIXED

        A case has been logged with Izenda Service  - Izenda Response:  We found an issue as reported and the fix is slated for our 6.10.0.6 release - May, 2016.

 

"14 On the styles tab there is an option for  "Show main report in Field | Value style".  When this is selected the value is automatically right justified and it cannot be changed."  - CLOSED

        A case was logged with Izenda Service  - Izenda Response: "This is by design. The field value visual group style has a visually fixed format."

"15. Issue with Subtotal under Advanced settings (gear).  There is a bug in the subtotal function under Advanced Field Settings."   - FIXED

If you choose (None) on this setting to remove subtotals from the column the report will fail with an “Object Reference not set to an instance of an object” error.  Setting this to another value such as “Count” makes the error go away, however this is not a solution, merely a workaround.

Fixed in 6.10.0.5 in April 2016.

 

"16 Problem with Date information Exported to Excel and Word in BI."    - FIXED

It appears date groupings have been converted to dates as stored by Excel, and never output as a date, so 04-2016 is changed to 42461  Issue is not limited to Excel or Word export, Date issues also affect reports using Group By (Month Name) causing an error.

Fixed in 6.10.0.4 in March 2016

 

"17 Dashboard Print to PDF produces multiple copies of one of the embedded reports."  - CLOSED

 Problem was found to be an extra instance of one of the reports that was embedded off the screen.  Previous versions of BI would allow side scrolling within the report window - a report was created in an older version which is not now accessible due to the side scroll functionality being removed. There is currently no way to replicate the issue.

 

"18 CSV Export in Business Intelligence is Broken."  - FIXED

 The CSV export in business intelligence produces repeating rows for one record in the report instead of exporting all of the data. Fixed in 6.10.0.5. in April of 2016. 

 

"19 The alias of TABLENAME, TABLENAME2 works fine in the general report fields and filters but does not work in expressions. If I join to a table more than one time and try to reference the second or third instance of the table in an expression, I get an error that the field does not exist.."  - FIXED

 This issue is resolved in version 6.10.0.11 released in early October of 2016. 

 

"20 The filter method "Use Previous OR" does not work if the field name is the same. I am joining to the same table from two different fields (a fiscal period) and would love to be able to use the Use Previous Or filter criteria. But if the field name is the same, it does not work. - FIXED

 This issue is resolved in version 6.10.0.12.

"21 Adding a field to a report which uses datasource reports as a Source causes ds-report fields that have been used as filters on the main report to get removed, and the ds-report datasource to disappear from the filter selection list."  - FIXED

 This issue is resolved in version 6.10.0.14.

 

"22 Security rights and BI dashboards - ." - FIXED

 This issue is resolved in version 6.10.0.12.

"23 Report Exports are generating TMP files - chews up drive space on server."  - FIXED 

 This issue is resolved in version 6.10.0.13.