Keys, SumIndexFields, and table relations in our examples
Thus far, we have created basic table definitions and associated pages for the WDTU project. The next step is to flesh out those definitions with additional keys, SIFT field definitions, table relations, and so on. The purpose of these are to make our data easier and faster to access, to take advantage of the special features of NAV to create data totals and to facilitate relationships between various data elements.
Secondary keys and SumIndexFields
The Playlist Line table default primary key was the one field Playlist No. In order for the primary key to be unique for each record, another field is needed. For a Line table, the additional field is the Line No. field which is incremented via the C/AL code for each record. So we'll change the key for table 50003 accordingly.
We know a lot of reporting will be done based on the data in the Radio Show Ledger. We also know that we want to report on data by Radio Show and...
