Release notes 7.2.5

Bug fixes

Megaladata Integrator: Before, using Content Security Policy resulted in an error on the Swagger UI page. If you used Apache to add an HTTP header Content-Security-Policy: script-src 'self' 'unsafe-eval'; object-src 'self' on the page /openapi/index.html, the page would be displayed as empty in the browser. The Browser console would return a Content Security Policy violation error. This issue occured due to the implementation of Swagger UI. In Megaladata, we developed an alternative solution (#11373).

Megaladata Desktop: If you middle-clicked on any of the links on the Megaladata Desktop home page ("Getting to know Megaladata", "Quick start", "News", etc.), the corresponding page would open not in the browser, but directly in the window. After that, the "Close" (×) button in the upper right corner of the window would stop working. The situation has been fixed, external links open in the browser window now (#10720).

Megaladata Desktop: Fixed a regression error "Access violation" that occurred on some computers when performing any drag-and-drop and caused the application to crash. The problem was often observed on computers with Intel(R) Pentium(R) CPU G2120 and Intel(R) Pentium(R) CPU G3260 processors. The error has been fixed (#11221).

SOAP Request: Fixed "Access violation" error that occurred after an error loading an invalid schema in a document array (#11180).

SOAP request: The program would fail to send a request to a SOAP service with digest authentication — the service would return error 401. Corrections were made (#11145).

Import from XML File: Fixed the error "XML file: Error importing XML. Error code: 7. Message: Error parsing XML document: Error parsing stream in row 0, position 0." that occurred when importing a root xml element of type anyType with specified xmlns without prefix (#11277).

Import from XML file: Improved performance when working with XSD schemas with a large number of root elements. Previously, when configuring import for such schemas, the application would freeze after selecting the root element in the Import from XML File node configuration wizard (#11072).

Import from XML file: In Megaladata 7, when enabling the setting "Validate against XSD", the program failed to perform validation against the XSD schema. We have added optional XSD validation for XML documents. Now, if you enable the "Validate against XSD" setting, activating the XML file import node will result in an error if the XML document doesn't match the schema (#9531).

Import from Database: A loop with a "until import succeeds" postcondition set on the Import from Database node, configured to ignore errors, was terminating prematurely. This issue has been fixed (#11211).

Import from Database: When reopening a package that had an Import from Database node configured with a request that used a variable of variant type, the error "Usage type 'Active' is not valid for the configurable variable..." occurred. This bug has been fixed (#11234).

Import from Database: When running the Import from Database node in a parallel loop, the errors "Insufficient system resources exist to complete the requested service" and "System error, (OS Code 1450)" occurred. Fixed (#11336).

Clustering: When simultaneously running multiple Grouping nodes which used the cluster number (previously obtained from the Clustering node) as the group and calculated quantity metrics, the outputs of the nodes were different. Additionally, the results varied in simultaneously running Cluster Profiles visualizers configured for the same port. This bug has been fixed (#11247).

Calculator: Locale is now used when retrieving a number to calculate a running total for a Calculator Expression of string type, with a value derived from numeric arguments. Without taking locale into account, calculations could have been incorrect.

Variable Mapping: For variables of Variant data type, the variable value editor in the "Configure Variables" window remained inactive after unmarking the "Null value" checkbox. This bug has been fixed (#11108).

Workflow Area: After moving workflow nodes with links, the functionality of selecting the output port when hovering the cursor (large blue frame) would disappear. The erroneous behavior has been fixed (#10694).

Workflow Area: After pasting a copy of a node into a Supernode and clicking the "Customize execution order" toolbar button, the execution order ports for that node were not displayed. The execution order ports would appear after moving the node or re-entering the Supernode. This behavior has been fixed (#11024).

Workflow Area: Inheritance and reference relationship arrows between parent and derived nodes are distinguished by unique colors (blue for inheritance, dark gray for reference). Previously, these arrows would incorrectly display as light gray after selecting and deselecting a workflow node. This issue has been fixed (#11225).

Workflow Area: The "Deactivate Node" button in the toolbar remained inactive even after the selected node finished executing. This issue has been fixed (#8322).

Job Scheduler: Corrected the hotkey hint for the Close (x) button in the upper right corner of the Scheduler Log window. The Scheduler Log can be closed with the keyboard shortcut Shift+J. Previously, the hotkey mentioned in the button's hint was Esc, but it did not work.

Connections: On the Connections page, the configured connections to Kafka, XSD schema set, and Tableau didn't have any information displayed in the Address line on the Connection tile, nor in the "Connection path" column (in case of a tabular page view). Bug fixed (#11376).

ClickHouse connection: When exporting to a ClickHouse decimal field, small negative numbers were converted to large positive numbers. For example, when running on Windows, exporting the number -0.000206 would result in 184467440737.09531016. In some cases (on Windows and Linux), an offset of 1 was observed in the least significant digit of fractional numbers. For example, when exporting 0.000206 to Decimal(20, 6), it was written as 0.000205. Corrections made (#11201).

MS SQL Connection: Fixed the "Access violation" error that occurred when the connection to the database server was lost during the export to database operation, when running on Linux (#11324).

MS SQL Connection: When running a Database import node, if the connection to the database server was lost while receiving data from the server, the node would freeze and could not be stopped. The issue occured on Linux, when connecting without using a client. This issue has been resolved (#11339).

MySQL Connection: There was an issue when reading large BLOB fields (over 65002 bytes) from the result set of a prepared query. The system would incorrectly read data from subsequent rows. This error has been fixed (#11186).

ODBC Connection: Fixed a situation where export to a database completed successfully, but not all rows were exported. This problem was observed on some drivers when more than 1 row was exported with records added to the table, for example, when working via SQL Server Native Client 11.0 (#8311).

ODBC connection: When using the 'mssqlodbc' driver on Linux to read values from decimal fields, an error occurred if the system's locale (the user's regional settings) used a different decimal separator than a period (e.g., a comma). This was due to a 'mssqlodbc' issue. A workaround has been implemented in Megaladata to address this issue and ensure decimal values are read correctly (#11190).

Oracle Connection: If there was an active connection to Oracle without a client and the connection to the server was lost (for example, due to problems in the local network), then after deactivating the node and re-establishing the connection to the server, re-activating Import from Database would fail with the error "Database: ORA-03113: end-of-file on communication channel", while the node would run successfully. The bug has been fixed (#11067).

PostgreSQL Connection: Under certain scenarios, the import from a database would freeze:

• When selecting n > 0 rows from a table [1000 *n + 1, 1000 * n + 50 * (n mod 21)], if the last field of the last row contained a 0-length line.
• When selecting rows from a table, if in any (1000 *n + 50 * (n mod 21))-th row, where n > 0, the last field of the result set contained a 0-length line.

This regression error appeared in version 7.2. Corrections were made (#11299).

PostgreSQL Connection: Queries of the type SELECT oid, * FROM pg_type caused the system to hang and their execution could not be stopped. In some earlier Megaladata versions, when executing such queries, the message "large object 11 does not exist" was displayed. Importing oid fields is supported now. Fields of the type oid are read as integer (#11115).

Database Connection: Fixed the "Access violation" error that occurred when multiple database connections were activated simultaneously. The error was observed on Linux for connections to PostgreSQL and MS SQL (#11264).

Database Connection: Previously, if a database connection was configured with the login prompt enabled and tested (using the Test button) without entering a password, then later attempted with a password (using the Connect button), the connection would freeze for about a minute and result in the error message "The timeout for entering the username and password for connection has expired". This issue has been resolved (#11359).

Application: Fixed the "Stream write error" that occurred when opening a corrupted Megaladata package, as well as when trying to open a working package that referenced a corrupted one. This regression error appeared in version 7.2.2 (#11271).

Application: In the port configuration wizards, the buttons for actions that cannot be performed (View, Run, and Back) are now hidden. The View button that was displayed on the last page of the SOAP Service, REST Service, and XSD Schema Set connection configuration wizards (#4634) is also hidden now.

Application: A node could be cloned while activating, whereas in this case the message "Node ... is blocked" should be displayed and the clone operation should not be performed. The error has been fixed (#11116).

Application: In the Date/Time editor windows (e.g., the dropdown calendar in the Row Filter configuration wizard), using the Up/Down/Left/Right keys to select a date didn't work: After selecting a date this way and pressing Enter, a different date would be displyed in the date field (usually, the date that was there before). Clicking Space would result in a date only, without time, but with a space in the end, entered into the date field. Such a date would be considered invalid by the program. Pressing Tab when you have a Date/Time editor open would result in an error "Cannot read properties of null (reading 'dateValue')". Bugs fixed (#11364, #11365).

Join: In the table join setup wizard, enabling the 'Show lost links' option would display the key fields (the fields by which the sets are linked) missing after input. However, disabling the option did not remove these fields, and repeatedly enabling it would add duplicate columns with the same caption. This issue has been fixed (#11165).

Visualizers Page: When attempting to delete a blocked visualizer (e.g. during a long visualizer activation), the error message "An error occurred while the program was running. Node ... is locked" was displayed, but the visualizer disappeared from the list. To see the visualizer in the list, the Visualizers page had to be reopened. The bug has been fixed, a blocked visualizer doesn't get deleted now (#6388).

Cube Visualizer: Previously, when you right-clicked a series in the Cube Chart, the program often displayed the chart context menu instead of the more specific series context menu. This erroneous behavior would occur under the following conditions:

• Chart type: Columns
• Tooltip type: Shared tooltips
• Significant X-axis scaling

This regression error first appeared in Megaladata 7.2.0. Fixed (#11342).

Cube Visualizer: In a Cube Chart with the following properties:

• Chart type settings: any but "Columns"
• Multiple points on the X axis (the distance between consequent points is rather small)
• Tooltip type settings: Shared tooltips
• The series has no value in the point where the cursor is located, but has some value in an adjacent point

– the series would be erroneously displayed in the tooltip. The issue has been fixed (#11346).

Cube Visualizer: The key bindings Alt+Home, Alt+Left, and Alt+Right, apart from calling the Cube commands, would perform browser commands. Using Alt+Home would not only make the user return to the start of the column but simultaneously open the homepage. Alt+Left and Alt+Right would not only move to the relevant table cell but also attempted to move to the previous or next page of the browser tab history. This regression error first appeared in Megaladata 7.2.0 and is now resolved (#11360).

File Storage: When trying to download multiple files, File Storage would display the error "Failed to execute 'showSaveFilePicker' on 'Window': File picker already active." If ignored, only the first file from multiple selected files would be downloaded. The error only occurred in Chromium-based browsers released a year ago or later. Fixed (#11138).

File Storage: Previously, when you entered an empty file storage folder and scrolled the page using the scroll bar or the mouse wheel, the file table would disappear from the screen. The table would show up again after you save some files to the folder. The issue has been resolved (#8552).

Export to Database: If auto-synchronization was enabled in the Export to Database node, and the case of field names in the receiving table changed, this change was not recorded by the export node. The node still tried to find fields with previous-version names. Corrections were made; now the Export to Database node takes into account the case of table field names. At the same time, linking input columns stays case-insensitive. The case of output columns is updated to match the database table. If the case of a field name in the database has changed:

• When auto-synchronization is disabled, executing the request will result in an error (as before), since saved names are used. You need to go through the setup wizard again.
• With auto-sync enabled, the Export to Database node will run without errors (#11226).

Export to Database: Fixed an "Access violation" error that occurred when performing export to a database table containing a field with a variant data type. The error was observed if the "Update existing table records" export type was selected in the Export to Database node setup wizard (#11080).

Other changes

Coarse Classes: In the visualizer and the Coarse Classes node configuration wizard, the table headers "Calculate Parameters", "Lock" and "Unlock" now have clickable icons. When you hover over these icons, the cursor changes to a "pointing finger".

Field mapping: When hovering over the "Delete all..." icon in the table header, the cursor changes to a "finger" shape. The "Delete all", "Stop all", and "Refresh" icons are now clickable (#7361).

Application: The error message "A local component already exists in {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXXXXX} identifier list" has been made more informative. Now, when trying to add references to 2 copies of the same package to a package, the message "Cannot add a local component with the caption "Caption" and the identifier {XXXXXXXXXX-XXXX-XXXX-XXXX-XXXXXX-XXXXXXXXXXXXXXXX}: an item with this identifier already exists in the list" (#6209).

Application: When a node configuration wizard page displays a table, after performing the "Delete All..." action using hotkeys, the table remains active.

Visualizers Page: Changed the behavior of the "Delete All" button on the Visualizers page. Previously, deleting visualizers was interrupted when the first locked visualizer was reached, now all unlocked visualizers are deleted.

Improvements

Calculator (Tree): When working with large input trees, users experienced delays when switching between Calculator expressions. We have optimized UI responsiveness, making expression switching significantly faster (#11338).