Gen Toolset RI constraint Attribute order differences

Products

• Gen
• Gen - Workstation Toolset

Issue/Introduction

The Gen 8.6 Toolset is listing the RI Constraint Columns in reverse order when implementing an Entity in the Data Structure List (DSL).
 
After making a change to a 'key' attribute in the Data Model List (DML), the table was dropped and reimplemented for the changed entity within the Data Structure List (DSL).
When the Table is reimplemented, it also reimplements the Table Indexes and RI Triggers Constraints that are associated with the table. The problem is, when the RI Trigger Constraints are reimplemented, it lists the key columns used by the RI Trigger Constraint in a reverse order from the related Index.

Is this a problem or not?
After generating the RI Triggers, the generated triggers used the key fields in a the SQL statement in reverse order, which does not appear to be a problem because the statements are “AND” statements.
Can this order be changed or corrected?

Environment

Gen 8.6 Workstation Toolset

Resolution

The Dialog box “Constraint property and summary information” and the DSL Index show different associations. They get to the same objects from different associations, so the order isn’t necessarily the same, but neither is wrong.  

1. The dialog box for the RI Constraints "Constraint property and summary information” will look at the LINKFK object (RI constraint) and displays it’s USES associations to the FLDLNKU objects (columns).
   
   
2. The DSL (for the Table and related Index's) starts at the RECDATA object and displays several different associations… once it displays the ENTRYPN (index)  then it displays it’s DEFNDBY associations to  FLDEPUS objects (columns). The FLDEPUS objects have an USAGEOF association to a  FIELDFK object, and then the FIELDFK objects have a SOURCE association to the FLDLNKU object (displayed in the other dialog). 

So in summary seeing differences in column order, upon implementing tables and related Relationships/Indexes in the DSL, will not cause issues either at generation time or at runtime and it is a result of the above explanation. This order of columns in the RI Constraints cannot be changed.