GeneXus Next - Known limitations

This is a list of issues or known limitations of the different components of GeneXus Next.

GeneXus Next Desktop

Although the goal is to have GeneXus Next Desktop  with the same functionalities that GeneXus 18 had and more, this is a list of GeneXus 18 functionalities that have not been implemented in GeneXus Next Desktop yet:

• Create & Edit these objects
  • Unit Test, UI Test, Test Stuite
  • Procedures with layouts (partial support)
  • Query. Object
• Data Types
  • Geography data type is not supported (nor its derived data types) because the SQL Server distributed within the GeneXus Next container is Azure SQL Edge, which does not support these data types.
• Other missing Tools
  • Indexer (work in progress)
  • Search (work in progress)
  • Debugger
  • WW Objects (work in progress)
  • Run GAM backoffice
  • Module Packaging
• Tools Menu
  • All Inspectors (all but design import, open api import)
  • Reverse Engineering (dbret)
  • Live Editing
• Build Menu
  • Export Reorganization
• Generators
  • RPG
  • Cobol
• Cultures and UI of IDE
  • Light color (work in progress)
  • Chinese Language

GeneXus Next Start

Below are some known issues that might occur when working with GeneXus Next Start:

• Test data loading is not performed for applications with two-level Transactions.
• An error occurs when modeling an application in Japanese language. In some cases, there is no error but the characters are not displayed when executing the app.

GeneXus Next Design Assistant

These are some temporary limitations:

• It only works on projects that have been created with GeneXus Next Start.
• The final design still does not comply with all DesignOps - Conventions, so you must first adjust them to import the design into a KB.