Navigation Comparison Between GeneXus 9.0, X, X Evolution 1 and 2

In GeneXus X almost all formulas can be resolved in the server and also several formulas (with similar execution plan) can be executed together (in the same SQL). Therefore, the navigation list changes completely in this case. More information

Fixed SACs referring to with formulas:

SAC 26866 : Implicit condition was incorrectly added.

This message indicates that the value will be the same for all records.

Order clause supports more formula attributes, as most formulas are evaluated on the server side. This is the reason for the message to disappear in this version. In those cases, a new warning appears: "spc0136: Order ATT is a formula in group starting at line n". More information

This message was shown for Find formulas used as Item Descriptions in Dynamic Combo Box or Suggest controls. This restrictions does not apply any more in GeneXus X, as of GeneXus X Upgrade 4.

See : Formulas , SAC # 26243

Now subtypes attributes inherit their control-info from the corresponding supertypes.

This is the default behavior in GeneXus X (as for Upgrade 4). So, during conversion process all subtype attributes with a default Control-Info will inherit the value from their supertype.

This also affects variables basad on Subtype attributes or based on Business Components with subtypes attributes.

So, if the variable/attribute is present on a web form, you will notice this new behavior looking at the object's navigation.

SAC # 24870

This compatibility issue has been fixed as of GX X Evolution 1 Upgrade 2. See SAC # 28095 for more details.

New specification controls for Methods and Link function:

"spc0023: Parameter %1 has wrong type <linking | for method> %2."
"spc0024: Not enough parameters <linking | for method> %1" 
"spc0025: Too many parameters <linking | for method> %1"

Previous GX versions didn't check the data type and the amount of parameters in Methods and Link Function. Therefore, some of these warning message can appears during specification time.

SAC #24456

New message warning when rules are not included:

"spc0158: Rules %1 not included."

As from X Evolution 1 when rules are not included, an spc0158 is shown during specification time (SAC # 26371).

In same cases, this warning could disappear because of a new validation in rules that depend on SDTs. (SAC # 26762)

Also new warnings could appears for those "call" rules containing a parameter that has not been initialized. Now the specifier validate that each input parameters in the called object is initialized in the caller. (SAC # 25706).  This apply also to GX X as from Upgrade 4.

Those Find formulas that is know will retrieve just one record are optimized.

SAC # 24780

Examples:

spc0023: Parameter FeriadoSACLocalID calling GX00Z0 has wrong type. (Rules | Source, Line: n)

This message does not appears as for GeneXus X ev1 Upgrade 1:

"spc0097: Rule 'confirmtrn()'does not apply to Business Component. Ignored."

The expected navigation for Dynamic ComboBox and Suggest in subtypes is as follows:

FILL SubtypeCode with <ItemValues>, <ItemDescription>
INTO SubtypeCode, SubtypeDesc
Order SubtypeDesc

Therefore, in some cases you will see that navigation changes the attributes in the "INTO" or "ORDER" clause:

FILL SubCityCode with CityCode, CityName in =GNTPAI(PaiCod)
INTO SubCityCode, SubCityName
Order SubCityName

And in other casues where the supertype attribute was mentioned in the Fill clause, now it shows the subtype, to be consistent.

This change applies as from X Evolution 1 Upgrade 4. See SAC 29670 for more details.

New message warning indicating that a redundant formula is not going to be automatically updated in some cases: 

 Attribute %1 which is redundant in table %2 will not be updated.

Lookup the spc0172 on Specification Codes from spc0150 onwards for more details.

The message could appears as from X Evolution 1 Upgrade 5.

See SAC 30329

The fix applies as from X Evolution 1 Upgrade 6.

This clause is needed in order to apply server paging optimization.

See SAC 30923

See SAC 30362

The fix applies as from X Evolution 1 Upgrade 6.

See SAC 30725

This change applies as from X Evolution 1 Upgrade 7.

See SAC 30922

This change applies as from X Evolution 1 Upgrade 7.

See SAC 31068

This change applies as from X Evolution 1 Upgrade 7.

See SAC 31213

This change applies as from X Evolution 1 Upgrade 8.

This is an optimization that applies only for Mysql DBMS. See SAC 31172

Let's see an example to know where the difference appears:

Suppose we have a two level Transaction with this formula on the first level:

AttFirstLevel = sum(AttSecondLevel) 

Navigation to evaluate: AttFirstLevel 

   Formula: SUM ( AttSecondLevel)

   Where: AttFirstLevelPK = @AttFirstLevelPK

   Given: AttFirstLevelPK  

   Group by: AttFirstLevelPK 

See SAC 31229 for more information.

This change applies as from X Evolution 2.

Let's see an the differences between Evolution 1 and Evolution 2:

TestId LIKE &cTestId;
TestName LIKE &cTestName when not &cTestName.IsEmpty();
TestDate >= &cTestDate when not &cTestDate.IsEmpty();
TestNumber >= &cTestNumber when not &cTestNumber.IsEmpty();
TestComments LIKE &cTestComments when not &cTestComments.IsEmpty();
TestIdST LIKE &cTestIdST when not &cTestIdST.IsEmpty();

TestId LIKE &cTestId;
TestName LIKE &cTestName;
TestDate >= &cTestDate;
TestNumber >= &cTestNumber;
TestComments LIKE &cTestComments;
TestIdST LIKE &cTestIdST;

This change applies as from X Evolution 2.

"spc0158: Rule <rule> not included."

See SAC 31439

This change applies as from X Evolution 2.

The above rule is not being considered in some situations and therefor some changes were introduced in GeneXus X Evolution 2 to fix it.

See Group Navigations that receive attributes as parameters

This change applies as from X Evolution 2.

See SAC 31770

This change applies as from X Evolution 1 Upgrade 8.

See SAC 32081
The case is displayed as a warning message, it applies since X Evolution 2 Upgrade 1.

See SAC 31638
The case is displayed as an error message, it applies since X Evolution 2 Upgrade 2.

This is an optimization that applies to conditions that refere Udp functions without attributes as parameters.

See SAC 32024 for more details.

This optimization applies as from X Evolution 2 Upgrade 1.

See Join Type and Join Location Specification  and SAC 32212 for more details.

This change applies as from X Evolution 1 Upgrade 8.

For instance, the error will appears for these rules when ProcObject and WebPanelObject does not return a value:

&value = ProcObject()
WebComp.Object = WebPanelObject()
Att = ProcObject.Udp()

See SAC 33892 for more details.

This control applies as from X Evolution 2 Upgrade 3.