Summary
Tables are used when developing forms in Visual Studio, and they appear to the user as pages in finance and operations apps.
Tables contain data such as transactional information, journal entries, products, and metadata such as system settings.
You can add EDTs and base enums to tables from your project in Solution Explorer or from the AOT to populate the Fields node in the Table designer.
Fields and field groups record data in rows and columns, like a spreadsheet. The Properties window allows you to specify not only the Name and Label of the table, but also the Table type, such as TempDB or InMemory, as well as the Primary index and Cluster index. Indices are created to speed up data retrieval in a table. They should be used if the speed improvements that are gained outweigh the cost to maintain the index.
A table should always have a specified clustered index so you can determine how the table should be organized, and a specified primary index so you can determine the unique key on the table. An index is required when you are creating a table relation of type Foreign key relation.
If two tables contain related data, such as multiple tables that are used to collect customer information, you should create a table relation on the Relations node of the primary table in the table designer. You can specify which fields are related and dictate if fields should restrict records in the primary or related table.