I'm trying to find the best table structure for a user table that stores Employee by shift date and time. This table will be populated via an API and will be used to create system logic and reporting, and searching by employee and datetime is vital. Having looked at base app tables I noticed that some tables like Change Log Entry use AutoIncrement field as a clustered key . And other tables like G/L entry do not have this for entry no. And then there are tables with a CODE field as primary. What are use cases and advantages of having AutoIncrement? One disadvantage I can notice is the table is automatically sorted by entry number irrespective of clustered keys (employee, datetime).
field(50200; EntryNo; BigInteger)
AutoIncrement = true;
Caption = 'Entry No.';