By Bogdana Botez at Microsoft Development Center Copenhagen
Context: The user gets overview information about the business on the Dynamics NAV Role Center page.
Figure 1 - Cue information in Dynamics NAV shows cue information seen by the user on the Sales Order Processor role center.
The overview information consists of summed-up numbers, calculated from business data, like for example how many sales orders are still open, how many shipments are ready to go, or partially shipped, how many documents are waiting for approval etc.
Problem: NAV stores data in tables. By definition, a table is a repetitive structure containing multiple lines, each line having a different piece of the information. But sometimes this repetitive information needs to be summed-up or otherwise synthetized, and presented as an overview.
Solution: Store overview information in a singleton table.
There are two ways of calculating overview information in NAV.
By using a FlowField. This applies for simpler calculations, like filtered or unfiltered counts, sums etc.
By writing C/AL code to perform custom calculations. Use this when:
- The way to calculate the overview is too complex for flow fields, or
- The data needs to be pulled from an external system (like Dynamics CRM, QuickBooks or any external integration).
Table 1 - Cue tables in Dynamics NAV shows some examples of singleton tables used for creating Cues.
|Table ID||Table Name|
|5370||CRM Synch. Job Status Cue|
|9042||Team Member Cue|
|9050||Warehouse Basic Cue|
|9051||Warehouse WMS Cue|
|9058||Warehouse Worker WMS Cue|
|9060||SB Owner Cue|
|9061||RapidStart Services Cue|
|9063||Relationship Mgmt. Cue|
|9069||O365 Sales Cue|
|9070||Accounting Services Cue|
Table 1 - Cue tables in Dynamics NAV