hotchill wrote:
Ok, but the tool reset the ordering here without any warning to me I believe.
You have two options to go back to v2.6 ordering:
1) do it automatically once, through a refresh. This is controlled by: ResetFieldOrderBasedOnTargetOrderAtRefresh. After the refresh, set this to false again. From then on you can use option 2)
2) do it manually by applying a field ordering to the entities which have a compound PK (the rest is not really interesting anyway for this particular issue). After that, set UseCustomFieldOrderingOnNewElements to true, so new entities etc get a field ordering set automatically to the order in which you specify the fields or when you reverse engineer new entities, they get the order of the target db element. To find the compound PK entities, use element search in the designer, select 'Entity' as searchable element and specify:
return p.EntityModel.Vertices.Where(e=>e.IdentifyingFields.Count() > 1);
If you want to keep the model as-is, you can also change your own code to deal with the alphabetical ordering, and leave it as-is.