Portal

Snowflake Native App features

• DM-537: In forms, hyperlink fields are rendered with insufficient height when a hyperlink value is present, making the value unreadable.
• DM-557: In the Semarchy Native Apps environment, deleting a data location with the option to drop the database schema content fails with the following error: Cannot drop the table because of dependencies, preventing the data location from being deleted successfully.
• DM-640: Third-party library upgrade: Apache CXF.
• DM-897: When a collection of records is exported in CSV or Excel format, spaces in the generated file title are incorrectly replaced with + characters.
• DM-921: While only SMTP or JEE notification servers are supported as defaults, the REST API allows non-email servers (such as JMS or File) to be set as the default for workflows or email notification enrichers.
• DM-922: The REST API allows configuring multiple notification servers as the default for workflows or email notification enrichers, even though only a single default notification server is supported.
• DM-970: When the -Dmdm.dataaccess.resolveIDMatchedRefsWithSamePubId=true system property is enabled, opening the business view of a child entity fails when its parent entity uses ID matching. Attempts to browse the child entity business view result in an unexpected server error: NoSuchViewAttributeException.
• DM-1022: When using the REST API to delete records from an ID-matched entity in continuous loads, existing golden records are incorrectly reported as not found, causing the delete operation to fail even though the records are present in the golden-record data (GD) table.
• DM-1094: In search forms, updating an existing value in a filter field prevents the list of values (LOV) from appearing, even though it still appears when the cursor is placed at the end of the field value or when the field is cleared and entered again.
• DM-1105: Mass update requests through the REST API return the status PERSISTED even when the update condition matches no data, suggesting that the operation succeeded although no changes are applied.
• DM-1132: In some environments, calling a stored procedure from a workflow automation step fails with a SQL syntax error. The CALL statement generated by the automation step is not valid syntax.
• DM-1263: Job logs and related repository artifacts are not purged according to the retention policies of the expired entities when another entity in the model is configured with a Forever retention policy.
• DM-1291: In custom search forms, manually entering a valid date in a date picker field does not enable the Apply button, preventing the filter from being used.
• DM-1321: Model deployment fails when the data location contains views prefixed with usr_ whose ownership or grant settings are incompatible with the data location user.
• DM-1327: In xDM on Snowflake using hybrid tables in Microsoft Azure, importing data through the REST API fails when the Semarchy Email enricher runs, returning the following type mismatch error: Cannot invoke <setter_method> on bean class <class> - argument type mismatch - had objects of type "java.math.BigDecimal" but expected signature "long".
• DM-1916: Third-party library upgrade: Netty.
• DM-1984: The REST API does not restrict the type or size of files uploaded as profile pictures. As a result, invalid or oversized files can be uploaded instead of being blocked.
• DM-2039: Third-party library upgrade: Jackson Core.
• DM-2045: Third-party library upgrade: Kotlin.
• DM-2048: Third-party library upgrade: Snowflake JDBC Driver.
• DM-2049: The OpenStreetMap enricher returns a 403 Forbidden error during record creation or enrichment, preventing address enrichment from completing successfully.
• DM-2068: Third-party component upgrade: Apache Tomcat for xDM preconfigured.