Release notes 7.0.3

Errors were corrected in several Connections to data sources, visualizers, Calculator, Coarse classes, Date and time components and also in the components included into Import, Data tree, Programming and Export groups. Megaladata system requirements changed for Linux. Installer was improved.


JavaScript: The following error was corrected: "Runtime is in exception state". It occurred when script execution process was stopped and error occurred in script in one and the same time. Most often, the error occurred in Preview of JavaScript node because in this case only the first 100 rows of the data set were processed and the script stopped (#9876).

Megaladata Integrator: Generation of "nullable": true was eliminated in OpenAPI for the properties that were not to take null value:

  • for the properties that match the node ports;
  • for the rows properties in the data set;
  • for the containers in the tree-like data structure.

The optional elements for which no value is specified are not recorded in the response json message of Integrator. In particular, now "Container": null elements are not recorded in this message for nonavailable containers in the tree-like data structure (#9793).

SOAP request: Duplication of Content-Length header in the request was corrected in SOAP request node. "Bad Request" error could occur in response to such request (#9850).

SOAP request: The following error was corrected: "No WSDL operation selected". It occurred when reconfiguring the SOAP request node to another operation with the same name but inside another service or port. For example, if two packages are published with the published supernode inside them with one and the same name, and the SOAP request node initially configured to the service operation from the first package is reconfigured to the same operation from the second package. In this case, the connection that uses the SOAP request node is configured to the root WSDL documentMegaladata Integrator /soap?wsdl (#9855).

Quick view: When working in Google Chrome in the Quick view node with large amount of data (for example, if there are very long strings in the data set (exceeding 5 million of characters)) the following browser error occurred: "Aw, Snap! Something went wrong while displaying this webpage.". In some cases the error didn't occur after data view but significant slowdown of Megaladata Studio operation was observerd, and it was required to restart the browser. The problem was solved. Now the string length for the quick view is limited by 5000 characters so that the browser could display data (#5776, #6166).

Data quality visualizer: The following error was corrected: "Cannot read properties of null (reading 'Calculated')". It occurred if the user configured the visualizer on the node with large data set, started calculation of statistics, went to the wotkflow in the next tab and deleted the node on which the visualizer was configured (#9810).

Cube visualizer: If the user opened detailing in the Cube and quickly moved along the cells of the Cube cross table, sometimes the detailing didn't match the selected cell. Such problem could occur also in other visualizers with detailing. Error of behavior was corrected (#9803).

Cube visualizer: The following error was corrected: "Cannot read properties of undefined (reading 'DimensionType')" (#9904).

Cube visualizer: The following error was corrected: "Could not convert variable of type (UnicodeString) into type (Integer)". It occurred in the Cube with the dimension related to the variable type while attempting to paste the random value to the search string using Ctrl+V or the toolbar button.

Statistics visualizer: The borderline case was fixed when the required point didn't get into the histogram when calculating quintiles. Due to an error the visualizer was not displayed in some data sets (#9839).

Tree to table: The container nodes with the used nodes disappeared in the Tree type ports after package closure and repeated opening. The problem was observed when automapping was enabled. Error of behavior was corrected (#7509).

Tree to table: Settings were reset after package closure and repeated opening for Tree to table node that was inside the Supernode with the enabled automapping at the input port. The situation was rectified (#9076).

Import from Excel: When specifying explicitly set range for the file that contained the same columns, the following error occurred on the second wizard page: "Invalid row/column index". A similar error occurred for any data set when specifying explicitly set range that included all rows or all columns (for example, A:B - all rows from columns A and B). The error was corrected (#9883, #5734).

Import from MGD: The following error was corrected: "Access violation at address". It occurred when changing the data type of the used column in the imported file. Such situation was possible, for example, if there were File 1 and File 2 that differed only by the data type of one of the columns, and data import was initially configured to File 1, then File 1 was deleted and File 2 was renamed to File 1 (#6990).

Import from database: The following error was corrected: "Client proxy object was finalized". It occurred after pressing on "Save" button in import from database wizard if the table for import was selected via the empty variable when configuring the table (#9745).

Calculator: If the user opened the expression for editing in the node wizard, changed its properties somehow, and then moved it up and down while the expression was in the editing mode, the changes introduced before moving were not saved. Error of behavior was corrected (#8306).

Calculator: ArcSin and ArcCos functions returned incorrect result. ArcSin(0)=1,57 instead of 0, ArcCos(0)=0 instead of 1,57. The error appeared in version 7.0.0. Corrections were introduced (#9862).

Calculator: StrToDate function description was updated in the node wizard. Changes were introduced into the following example:

  • format with MM/DD/YY/HH:NN:SS was replaced with MM/DD/YY HH:NN:SS,
  • the date/time string was changed from 12/25/04/12:44:54 to12/25/04 12:44:54.

Coarse classes: If the Date/Time field was selected as the input field, the real Date/Time values were displayed in the Coarse classes node wizard, although the values in Class parameters port were correct. The error was corrected (#7612).

Coarse classes: Access violation at address error was corrected. The error ocurred when the user performed some actions to edit binning while clicking on the bound cell (#8666).

Coarse classes: The lower class bound differed from the upper bound of the previous class in the coarse classes table. If the upper bound of the first class was edited in the interactive visualizer window of the node wizard, and then the upper bound of the next class was changed, also the lower bound of the second class was changed after pressing Enter. In this situation the lower bound of the second class must not change and it must match the upper bound of the previous class. The error was corrected (#8679).

ClickHouse connection: The memory leak error was corrected. NULL values support was added for the parameters in parametrized SELECT requests.

PostgreSQL connection: Materialized views (Materialized View), partitioned tables (Table Partitioning) and foreign tables (Foreign Data) were not displayed in Import from database wizard. The situation was rectified (#9898).

SOAP service connection: If the path was specified to the file in which namespace prefix used in the schema was declared in wsdl:definitions element, when configuring connection in WSDL Source field, the following WSDL load error occurred when testing connection: "libxml2 error (code 3004): Element '{}element ', attribute 'type': References from this schema to components in no namespace are not allowed, since not indicated by an import statement." The error was corrected (#9844).

SOAP service connection: When configuring the SOAP request node on Select request method page, there were no elements matching the published package if connection to SOAP service was used. WSDL source was the root WSDL document Megaladata Integrator /soap?wsdl in it. Error of behavior was corrected (#9851).

SOAP service connection: Access violation at address error was corrected. It occurred when connecting to SOAP service if the schema contained complexType with mixed content (#9864).

XSD Schemas Set Connection: The error in processing of simpleContent extension construction was corrected. This error caused absence of child elements of the root element (#9868).

Table to tree: There were no several nodes in the output port of Table to tree node in the presence of nested arrays. The error was corrected (#9887).

File storage: When opening the package from the read-only folder, an error occurred, and the package could not be opened. It is a regression error. Corrections were made, and now the package is opened without the right to save changes, and the user receives corresponing message (#9861).

Export to text: The multiline values (the string values that contained line breaks) were exported without framing quotation marks. In the result, the string value was broken up into different strings without any information on the fact that it was to be one string. In case of the subsequent import, the file structure could be damaged, data was read not as one string but it was divided into several values. The export error was corrected (#9683).

Export to text: When exporting the strings with non ASCII characters to the file with the fixed column width, the column width in the received file was not the same. The error was corrected (#9905).

Export to text: The characters that were not supported by encoding of the exported text file were replaced in Megaladata for Windows with the character with 0x3F code, and in Megaladata for Linux with 0x1A. Uniformity was provided. Unsupported characters will be replaced with 0x1A (#9920) in both systems.


Megaladata Server: To define IP address of the client who connected to Megaladata Server via WebSocket via Proxy server, X-Forwarded-For header is used. Now in logs and in Session Manager of the Administration section the whole chain of IP addresses is displayed — Source IP -> IP proxy 1 -> IP proxy 2. Previously, client IP was defined as IP proxy 2 (#9541).

Installer: It became possible to select the base server image in the installer interface for Linux. One more --from_image parameter is added to the parameters taken by the script behind which the user must specify the required base image from the ones available in server/Dockerfile. Before the server image construction availability in server/Dockerfile is checked, if the image is not found, the script operation is terminated with an error (#9809).

Installer: megaladatad.socket file was transferred to %ProgramData%\Megaladata folder from %ProgramData%\Megaladata\Server subfolder (#6640).

Installer: When installing Standard and Enterprise editions by Megaladata Integrator, "OpenAPI service description" page shortcut is created(#9673).

Logging: Logging of large messages from JavaScript when logging to journald became possible.

Changes in the System Requirements

  • The minimum supported version of Linux 5.3 core
  • The minimum supported version of docker 20.10.0.

Other Changes

Megaladata Community Edition: Some users of Megaladata CE face the "first launch problem" when the window is opened, but the interface is not displayed while attempting to launch the application. But the repeated launch enables to start the work. To solve this problem, option to start Megaladata CE with the command line argument --disable-cache was added. After Megaladata CE update it is required to open the shortcut properties and add space-separated --disable-cache at the line end in "Object" input editor.

SQLite connection: Import and export for the encrypted database became 25% faster. Performance improvement will be observed for the connections created in Megaladata 7.0.3 (#8213).

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