We will create a Vehicle group table. We don't have much choice on the name in this as it has to start with our prefix, and end with Group; therefore, it will be ConWHSVehicleGroup. To create this table, follow these steps:

1. Using the recipe for creating EDTs, create a Vehicle group EDT using the following parameters:

2. Save the EDT, but don't close the designer.
3. From within the project, choose to create a new item.
4. Choose Data Model from the left-hand list and select Table from the right.
5. Enter ConWHSVehicleGroup in the Name field and press Add.
6. This opens the table designer in a new tab. From the project, drag the ConWHSVehicleGroupId EDT on top of the Fields node in our table, as shown in the following screenshot:

7. This creates the field with the same name as the EDT. As this is our table, we should remove the prefix and name it VehicleGroupId.
8. We can now complete our EDT, open the ConWHSVehicleGroupId EDT (or select the tab if it is still open), and enter ConWHSVehicleGroup in the Reference Table property.
9. Right-click on the Table References node and select New | Table Reference.
10. In the property sheet, select the Related Field property and then select VehicleGroupId from the drop-down list.

11. Save the EDT and close its designer. This should make the active tab the ConWHSVehicleGroup table designer; if not, reselect it.
12. From Application Explorer, which is opened from the View menu, expand Data Types and then expand Extended Data Types.
13. Locate the Description field, and drag it onto the Fields node of our table.

14. We will now need to add an index; even though this table will only have a few records, we will need to ensure that the ID field is unique. Right-click on the Indexes node and choose New Index.
15. With the new index highlighted, press F2 and rename it to GroupIdx. Change the Alternate Key property to Yes. All unique indexes that will be the primary key must have this set to Yes.

16. Drag the VehicleGroupId field on top of the new index.

17. Open the field's properties and set the Mandatory property to Yes, AllowEdit to No, and leave AllowEditOnCreate as Yes.

18. We can now complete the table properties, select the table node in the table design (the table name), and complete the property sheet as follows:

19. We will now need to create a field group; as we will use a Simple list design pattern for this type of table, we will only need one. Right-click on the Field groups node and select New Group.

20. Select New group and rename the group to Overview by pressing F2.
21. Create a label for Overview.

22. In the property sheet, enter Overview as the Label property and click on the lookup button to locate the label we created in the previous step.

23. Drag the two fields onto the group and order them so that VehicleId is first in the list.

24. In order for any automatic lookups to this table to show both ID and Description fields, add both fields to the AutoLookup field group.

25. We can skip to the Methods node, where best practice dictates we need to provide the Find and Exist methods.

26. Right-click on the Methods node and chose New Method.

27. The code editor has changed in this release so that all methods are shown in the same editor. We are given a method stub, as shown here:

/// <summary> 
/// 
/// </summary> 
private void Method1() 
{ 
} 

28. Remove the XML documentation comment section and create the Find method as follows:

public static ConWHSVehicleGroup Find( 
      ConWHSVehicleGroupId _groupId,  
      boolean _forUpdate = false) 
{ 
    ConWHSVehicleGroup vehGroup; 

    vehGroup.selectForUpdate(_forUpdate); 

    select firstonly * from vehGroup 
        where vehGroup.VehicleGroupId == _groupId; 

    return vehGroup; 
} 

29. Create a blank line above the method declaration and type three slashes (///), which causes Operations to create the XML documentation based on the method declaration. Fill in this documentation as follows:

/// <summary> 
/// Returns a record in <c>ConWHSVehicleGroup</c> 
/// based on the _groupId parameter 
/// </summary> 
/// <param name = "_groupId"> 
/// The Vehicle group ID to find 
/// </param> 
/// <param name = "_forUpdate"> 
/// True if the record should be selected for update 
/// </param> 
/// <returns> 
/// The <c>ConWHSVehicleGroup</c> record 
///</returns> 

30. Now, to create the Exist method, go to the end of our Find method and create a new line after the method's end brace and just before the final brace for the table, and type as follows:

/// <summary> 
/// Checks if a record exists in <c>ConWHSVehicleGroup</c> 
/// </summary> 
/// <param name = "_groupId"> 
/// The Vehicle group ID to find 
/// </param> 
/// <returns> 
/// True if found 
/// </returns> 
public static boolean Exist( 
                    ConWHSVehicleGroupId _groupId) 
{ 
    ConWHSVehicleGroup vehGroup; 
    if (_groupId != '') 
    { 
        select firstonly RecId from vehGroup 
            where vehGroup.VehicleGroupId == _groupId; 
    } 

    return (vehGroup.RecId != 0); 
} 

31. We will have two tabs open, the code editor and the table designer. Since the code editor will be open, close this first, saving the changes. Then close and save the table designer.

32. Finally, we will need to synchronize the database so that the table is created within the SQL Server. Before we do this, we will need to build the model by following these steps:
    1. From the menu, select Operations and then Build models....
    2. Check ConWHSVehicleManagement from the list and press Build.

33. To synchronize the database with the table definitions, right-click on the project in the Solution Explorer and choose Synchronize ConWHSVehicleManagement with Database.
34. This will start the process and will be visible in the Output window. We will only need to do this when we need to either run unit tests or tests within our environment.