Skip to main content
Version: v2.6

Release 2.6.2

Issues fixed​

Accept @value attribute on count file for file based staging load (ticket: 4613)
Fixed an issue where a previously valid format of the adjacent count file for a staging load file failed. Specifically, the runtime now again accepts the row count inside a @value attribute.

Valid formats are:

  • Simple number:
    • 123
  • Root format (RowCount/Count as root element):
    • <RowCount>123</RowCount>
    • <Count>123</Count>
    • <RowCount value="123" />
    • <Count value="123" />
  • Nested format (root element name is not significant):
    • <Root><RowCount>123</RowCount></Root>
    • <Root><Count>123</Count></Root>
    • <Root><RowCount value="123" /></Root>
    • <Root><Count value="123" /></Root>

Improved diagnostics on attempted creation of an invalid index (ticket: 4611)
Setup of the Source Engine or optimize of View queries intermittently attempts to create an invalid index (with no index columns). The behavior is linked to the indexes already in place on the targeted table and this makes it difficult for Hopp to identify the core issue.

The reported error in the job log is now improved in order to provide diagnostics information to assist a long term resolution.

The job log also provides a workaround to the user in the form of dropping all non-clustered IX_Mig_* indexes on the target table and restart the job.

Fix Studio Clean up Workspace (ticket: 4610)
Fixed an issue where the Clean up Workspace function in Studio failed with an InvalidOperationException

Do not generate Source Engine Interface Parsers for incomplete Business Objects
Fixed an issue where the Source Engine Generator produced InterfaceParser code for Business Objects marked as incomplete in the Source Map. Studio validation ignores incomplete Business Objects, which may lead to non-compiling InterfaceParser code.

With this fix, no InterfaceParser is generated for Business Objects marked as incomplete in the Source Map.

Fix duplicate in Constant replacement (ticket: 4616)
Fixed an issue, where the ValueResolver in charge of the substitution of Constant references {constant:ConstantName} in other constant values in some cases failed with a duplicate error.

This happened when a constant in the Source Engine and a constant in the Target Engine had the same name, differing only in casing.

Issue with invalid XML character in Event parameter (ticket: 4617)
Fixed an issue where an invalid XML character in a parameter value for an Event caused a runtime exception in the style of:

ArgumentException: '', hexadecimal value 0x1A, is an invalid character.

With this fix, any invalid XML character in an Event parameter will be replaced with a space.

Add debug option to OpenID Connect
Debugging the OpenID Connect integration for external authentication has been improved by adding a new configuration setting, DebugExternalAuthLogging, that causes the Portal to output tokens and claims in the log when enabled.