Table of contents


Development Environment

Web Development and Improvements in user experience

(Productivity and Enterprise-level Application Development Features)

Ajax Overview, [[21759|GeneXus'>Ajax'>Ajax Overview, [[21759|GeneXus and Ajax]]

Business Components

Business Component - Publication as an Enterprise Java Bean

Practical course: Bluesky Charters

Application Localization

Application Localization
Translation Tool
Help "in any language"
Practical course: Bluesky Charters


About this topic
Patterns based development
Built in Patterns
Work With Pattern
Demo: Work With Pattern
Practical course: Patterns

Better data model

Null handling optimizes navigations
Nulls property


User experience

New options on rightclick in win

Reverse Engineering

Database Reverse Engineering Tool

New Platforms

.Net Mobile Generator
More J2EE support than ever

Data Types and Methods

Message Queue handling data types

LDAP Data Type

URL access Property
New IIF function
New byte count function
New Methods for attributes, variables and enumerated domains!
XSLTApply Method
Procedures can now call web objects
Web Services: Grouping Locations
News about model, object, and control properties

This is not the latest version of this document; to access the latest version, click here.
Unofficial Content
  • This documentation is valid for:

GeneXus 9.0 Upgrade Course


Real-world entities as defined in GeneXus usually have a field that describes/identifies them. For the application's users, this field may be the one that identifies the entity. As from GeneXus 9.0, you are able to specify which attribute is the Description Attribute for each Transaction level. Tools like Patterns and GXPlorer take this information to improve the user experience.


The concept behind it is very simple, just think of the CustomerName of the Customer transaction or the ProductName of the Products transaction. See Description attribute for more details.

You can set them as description attributes as follows:

Only one attribute per level can be set as the description attribute. It may be a formula attribute.

By default, the first non-key attribute of the level whose data type is character (Character or VarChar) and that is not a foreign key is set as the description attribute. If all level attributes are keys, the last attribute of the level is chosen. There may not be a description attribute (either because no suitable attribute is found, or because the user explicitly chooses not to have one).




Last update: November 2023 | © GeneXus. All rights reserved. GeneXus Powered by Globant