FAQs - GeneXus Core course (v18)

Autonumber the second level of a transaction

You have a two-level transaction, representing a 1-N relationship with a weak entity. The 2nd level primary attribute has the property Autonumber = True, or is based on an autonumbered domain.



A warning is displayed in the Impact Analysis Report indicating that the value Autonumber = True will be ignored in the CityId attribute.



Solution:

Define the Serial rule in the Country transaction, to generate the autonumbering of the CityId attribute. For this you must define an auxiliary attribute in the head to store the last assigned value: