Release Notes 1.11

Modified on Fri, 1 Mar at 8:20 PM

New and Changed features


Studio

  • New validation rule 197 Field {0} with data type {1} is too large to be used in a relationship lookup when using char(*) field in a lookup in the Extraction Map of a source object (the resulting index created by the Source Engine setup would be invalid)
  • Fix that Import Rule Implementations in the Project Explorer context menu did not update the Pending Changes tool window


Portal

  • When inspecting the Source data of a Business Object, the Portal will now show the names of the Business Object copies and the Extraction Map Objects to correctly reflect the naming in the Studio Source Map


Engine Framework

  • Modified to supply the improved naming in the Portal Source data view
  • Fix error in generated source engine when passinğ a boolean Constant value as parameter to a View


Libraries

  • Modified to supply the improved naming in the Portal Source data view
  • Fix error in generated source engine when passinğ a boolean Constant value as parameter to a View


VsExtension

  • Fixed that local debug from Visual Studio was not working after port to Net 6.0


Director Runtime

  • Modified to supply the improved naming in the Portal Source data view
  • Fix error in generated source engine when passinğ a boolean Constant value as parameter to a View
  • Improved error message in job instance log if the Index Analyzer fails when creating an index 
  • Removed limitation of 512 characters on saved relationship value in the Target Engine


Director Client

  • Optimized local debug. The client now caches the Director Runtime locally, and will only download the runtime from the master in case versions differ
  • Fixed error that new tracking baseline was not set current when created


Director ClientService

  • Added operation to support Director Runtime version query


Installation and Refactoring

  • Database
    • Please back up all database before running refactor scrips
    • Run attached MigrationDb.09.sql in all Migration databases

  • Workstations
    • Reinstall Studio
    • Reinstall  Engine Framework
    • Reinstall  Libraries
    • Reinstall  Director Client
    • Reinstall  VsExtension (according to Visual Studio version)

  • Master Server
    • Redeploy Portal
    • Reinstall Director Runtime
    • Reinstall Director.ClientService

  • Visual Studio engine projects
    • Update to Net6.0
    • Ensure that NuGet Package Reference versions are correct
      • Microsoft.EntityFrameworkCore.SqlServer: Version=5.0.17
      • System.Data.SqlClient: Version=4.8.2

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article