Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Dashboards that were created at 5.8 or earlier were upgraded to 5.9 in such a way that if they were then exported and imported into a different instance, the views in the dashboard sometimes became disconnected from the dashboard frame and could only be removed from the screen be reloading the application. This fix corrects the original issue in unmigrated dashboards, and also fixes dashboards that have been migrated.


Views

Pie Charts

Fixed: The pie chart configuration screen was showing #labelAttr due to a missing translation.

Pivot Views

When creating a Pivot View, A pivot column source can be set to an Expression referencing a lookup pipe that is used to generate the pivot columns. If the lookup pipe is self referencing on the stream for a Pivot View, then it is getting the columns from the previous stream set in instead of the latest streamset. It now correctly creates the pivot columns using the latest streamset.

Show the record count in the page status/navigation bar for Pivot Views.

When setting up a Pivot View, a label attribute can be specified. If the same label is used by more than one Pivot column, the view now fails with a message giving the name of the label and which column its already been used on.

When count() was being used in a Pivot View value attribute, it was wrapping it inside a sum() aggregate by default. It now correctly allows a count() to be used as a pivot value.

Streams

Users can now use the internal variable _outputMultiplier in stream attribute expressions instead of "_type". _outputMultiplier is just an alias for _type and contains an element of the result of the Stream's "Output Multiplier" expression. See help on Stream output multipliers for an explanation of this advanced feature.

In memory stream caching limits were including update counts for streams items, when they should only be for stream items created. It now correctly controls the in memory stream caching for stream sets created.

Pipes

Directed Mode

Default worker size wil now be equal to either of the two: default buffer size, constant value of 1000, which ever is less. Even when worker size is set it will be restricted to either the value set or max buffer size / number of workers whichever is less.

Filters

Filters that contained empty sub-clauses sometimes generated invalid sql.

Analysis

When a Task plan fails and is re-run Analysis is run on on the previously failed task within the Task plan which has an incomplete Stream Set and also for all tasks with incomplete Stream Sets following this task in the Task plan which had not yet been run.

Collectors & Exporters

File Collectors

...

Excel file collectors failed occasionally when interpreting the time part of a date-formatted field.

Error messages for File Collectors now show (where relevent) the file name, line number and error class name.

Database Collectors

Database Exporters

Email Accounts

Scripting

Functions

Export / Import

Copying a stream caused duplicate actions and attributes to be created in related streams; this is no longer the case.

System Administration

Active Directory

...

Stream publishing no longer fails if the stream table's primary key and index on primary key column don't share the same name.

Logging

Unprocessed

...


Report General Error messages for File collectors and - show file name, line number and error class name.
Lookup pipes are now prevented from using any strategy other than default. In such case a WrongStrategyException exception will be raised.
When data is excepted on a pipe. No error message was generated to the console when there was no data. Now correcly shows the error message.
MySQL / MariaDB  collector queries now reflect column aliases in select statements i.e.

select abc as "Def"

previous this returned the attribute "abc", now it returns "Def"
Analysis and rollback of partitioned tables on SQL Server could fail with a 'Deadlock Detected' message. This failure was observed when many users were using Action buttons to run task plans on the same transactional stream, and when running analysis to populate many periods of data in Daily or Monthly streams, and only when running under heavy load.
The original error of discarding messeges without PhixFlow variables referenced has been resolved.