Release notes 7.1.0

In the new version, we made fixes to the application, the Export group components, database Connections, Association rules, and other components.


Megaladata Server: The error that occurred in the Session Manager while attempting to stop the package execution in the session created from BatchLauncher was corrected. After clicking on "Stop" button the following message was displayed: "Null reference to object". But the package was still being executed. The package execution stops after introduced corrections, no errors occur (#10110).

Megaladata Server: The old session identifier was displayed in the Session Manager after its restart. Namely, the identifier of the session and the date of its creation didn't change. The error occurred when starting specially prepared workflows. Under normal conditions of the product use the error was not reproduced. Corrections were introduced (#10111).

Megaladata Server: In the case of the multiple sequential starts of batch processing in the Session Manager for the sessions created from BatchLauncher, sometimes "Deleted" was incorrectly displayed in Activity column during the package execution. The error could occur when starting specially prepared workflows. Under normal conditions of the product use the error was not reproduced. Error of behavior was corrected (#10112).

Python: When using Python 3.9.x, start of scripts inside the Megaladata process caused "Access violation" error. It appeared in version 7.0.0. The required corrections were introduced (#10065).

Association rules: "Access violation" regression error was corrected. It appeared in version 7.0.0 and it occurred if the user stopped the node training process, entered the wizard, changed any parameter, saved the settings and started the node retraining (#10067).

Association rules: If "Out of memory" error occurred when training the node, after settings changing and repeated node training the output port remained empty, and while attempting to execute the node, a message appeared with information that the node was not trained. It was impossible to train other Association rules nodes in the current workflow using the same data. It is a regression error and it appeared in version 7.0.0. Corrections were introduced (#10069).

Association rules: Not all rules satisfying minimum reliability could be selected because of the rounding error. The error was corrected. The rules were checked for the minimum reliability with the accuracy up to the whole percentage (#10091).

Association rules: "Access violation" error was corrected. It occurred if large data sets were supplied to both node inputs, nodes were configured (elements and transactions were set) and then the node training process was started and terminated (#10094).

Data quality visualizer: The following error was corrected: "Cannot read properties of undefined (reading 'isGroupHeader')". It occurred when activating Data quality visualizer from the Reports page without prior entering the visualizer from the Visualizers page (#9470).

Table visualizer: The following error was corrected: "Data set is not in the closed state". It occurred if the user set the sorting by ~20 columns in the table with many columns (~200), quickly went to the workflow opened on the next tab and deactivated the node on which the visualizer was configured (#9963).

Table visualizer: Auto selection of the column width by the header text didn't work for some columns due to rounding and difference in 1 pixel. The problem is typical of somebrowsers (for example, Chrome). Corrections were introduced.

Grouping, Table to variables: For the columns that relate to the integer type and contain the values that are more than 253 - 1 or less than -253 + 1, errors can occur in aggregations: Minimum, Maximum, Mode, First, Last, Single. When calculating the unique values count, different unique values could be counted as one. The required corrections were introduced, indicators are calculated without loss of accuracy (#9943).

Import from MGD: If the output fields were deleted for the data set with one column in the output port, the field related to the Variable type was added and they were connected afterwards, the following error occurred when starting the node: "Metadata does not comply with the previously declared metadata" (#8426).

Import from MGD: When connecting the fields related to different types with the field related to the Variable type, the following error could occur: "Unsupported Variant subtype" (#8427).

Coarse сlasses: Opening of the wizard of the Coarse сlasses node in the page browser following the link received using Share button, caused the following error: "When switching to "Coarse classes. Configuration", the error occurred. Cannot read properties of undefined (reading 'PrepareFilterField')". The error was corrected.

Logging: Screening of the string parameters values was added for the log parts that are recorded in JSON format (parameters). Now the parameters related to the Boolean type instead of True and False are recorded as trueand false.

Desktop application: The following problems were solved: incorrect display of the application window when the desktop Megaladata edition with two display monitors was used, namely:

  • when dragging the application window from one screen (the larger one) to another one, a part of the window was covered with the grey panel (#9024);
  • when dragging the application window from the larger screen (~4К) to the smaller one, the window didn't change the scale automatically (#9091);
  • f the application was deployed two times to full screen using Win+Up keys on the left screen, a part of the window was displayed on the right screen (when using one screen, a part of the window was under the Taskbar(#8296).

Desktop application: When opening any package (to open using Megaladata) or just when starting Megaladata Community Edition, the application window was opened but the interface was not displayed. It was possible to close this Megaladata Community Edition window only using the Sesson Manager. The repeated application launch was successful. The problem of the first launch was solved (#9720).

Neural network (Classification): "Not trained neural network" error was corrected. It occurred in the Neural network (Classification) node, the layers configuration of which was set using the control variables. The error could occur after repeated opening of the package and activation of the trained neural network, and also if the clone of such neural network was activated (#10137).

Workflow outline: After cancellation of the process executed for a long time via Processes Panel (for example, JavaScript node with the loop equal to 100,000,000 iterations), the node activation animation was preserved in the workflow outline, some interface elements were not available. The error was corrected (#6246).

Workflow outline: The cloned node appeared far from the source one if the source node was located far from the left upper corner of the workflow outline. The further the node was located from the left upper corner of the workflow outline, the futher the cloned node appeared from it. Error of behavior was corrected (#4908).

Workflow outline: If the scale was changed using the "Workflow map" function, the node was added to the workflow outline in the right lower corner, then the package was saved and closed, and the coordinates of the added node were incorrect after saving the package in 100% scale. The node was located in the lower corner of the visible workflow part. But it was to be located in the same place where it was added when changing the scale. The error of coordinates saving was corrected (#10097).

Connection with databases: The following error was corrected: "Login failed for user...". It occurred after opening of the package with preset connection to database with the password that contained more than 32 characters when activating or testing the connection. When saving the package, the password was cut up to 32 bytes, and in the result, the connection to database didn't work after the repeated opening of the package (#9462).

Connection with databases: When database and server connection was lost, start of Import from database node execution was finished with cancellation of the node execution. Namely, the node was not executed, and the user received no messages. The situation was rectified. Upon database server connection loss, Import from database node execution was finished with an error message (#10049).

XSD Schemas Set Connection: The following error was corrected: "List index out of bounds". It occurred in Configuration of XSD schemas set wizard when adding two schemas to the list and deleting them one by one (#9522).

Supernode: When adding 5 or more input or output ports to the supernode and selecting the port type, after saving it was not possible to change the type of any of the previously added ports. The error was corrected (#10123).

Application: The following situation was observed in Table, Property inspector and Session manager visualizers: the cell was not selected in the table after right-clicking, and the context menu displayed the items for the previous selected cell. Error of behavior was corrected (#8104).

Application: "Cannot read property 'NodeIndex' of null" error was corrected. It occurred if the user only with the administration rights opened the package from the file storage. Now, in this case the explanatory message is displayed (#6787).

Application: The pop-up tip was not hidden in the wizards for the link for which there was no field. Such a situation could arise, for example, if data was supplied to the second input port in the Binning node, connection was set with the usage type in the wizard for any input field, then the fields or usage types were filtered in such a way that the connected field didn't fall under the filtering criterion (it was hidden). The tip previously displayed for connection was not hidden. Error of behavior was corrected (#9955).

Application: The first week day and the text of the Current Date button were not localized in the Date/time value entry editor (for example, it is used in Row filter node). The error was corrected (#10096).

"Connections" page: "Cannot read property 'getStore' of undefined" error was corrected. It occurred if "Connections" page was closed while testing the connection being activated for a long time (#8763).

Condition: Move up and Move down buttons were available in the wizard in the absence of ports (if the wizard was opened just after adding the node to the workflow outline). Error of behavior was corrected. If there is nothing to move, the buttons are not available (#10013).

Condition: If 2 ports were set on the page of "Configure list of ports" wizard, and then the second port was moved up, the numbering of ports (rows in the table containing the list of ports) was broken. Both ports were numbered 2. The error was corrected (#10014).

Export to Excel file: "Sheet name not set" error was corrected. It occurred in the Export to Excel file wizard when using the variable as the value of the Sheet name parameter after clicking on Next button at the first wizard step (#10081).

Export to MGD file: If the node execution was stopped (by pressing the node) while exporting to MGD file for a long time, the node moved to "Successfully executed" state anyway. It is a regression error and it appeared in version 7.0.0. Corrections were introduced: the export node execution of which was terminated remained grey, and it was specified in the Processes bar that processing was terminated (#10028).

Export to MGD file: When Export was performed from MGD, TXT, Excel import or from Loop, when rearranging the fields that contained null values, the fields were exported incorrectly: false, 0, 0.00, 00:00 or empty rows appeared instead of null values according to the type; null values appeared instead of non-zero values. The error was corrected (#9896).

Export to MGD file: "Access violation" error was corrected. It occurred when activating the node in the input port of which all fields were deleted with the exception of the field related to the variable type (or the field related to the variable type was moved to another position in the list). In this case, the input data set came from MGD, TXT, Excel import or from Loop nodes (#9612).

See also

Low Code Analytics at Top Speed
The Megaladata platform employs methods that ensure high-speed processing, efficient memory use, and easy scaling. Let's take a deeper look at what enables the platform's high performance and explore the...
Megaladata: What's under the hood?
The article describes the technological basis of the low code Megaladata platform — its components, architecture, frontend and backend, functionality, and performance. We intend to answer the most...
Cohort Analysis: Why Is It Valuable?
Every entrepreneur striving for effective business management comes to ask themself a question: What is the income brought by one client?

About Megaladata

Megaladata is a low code platform for advanced analytics

A solution for a wide range of business problems that require processing large volumes of data, implementing complex logic, and applying machine learning methods.
It's free