Layouts can reference any field in any table in the local data, but the data that is fetched is valid only if Sales has “synced” to the table. Syncing means that Sales sets the table “pointer” to the relevant row; all fields in the row are then available to the layout.

 

Note: Layouts don’t use lookup fields to find an applicable row – they simply start grabbing the fields in the “current” row in the table; syncing by Sales causes the relevant row to become the “current” row (i.e., the row that is pointed to by the table “pointer”).

 

This section describes the tables that get synced for all types of layouts. The following table shows all of the tables (and the fields used to sync) available to Text Merge and Shared Text Merge layouts. The section Tables and fields available from Graphic layouts shows all of the tables (and the fields used to sync) available to Graphic layouts. The tables listed are all those that you can legitimately reference from your layout (that contain data relevant to the transaction). The Printing table is a special case: Sales writes a record to the Printing table previous to printing and the layout fetches most of the data it uses from this record. For descriptions of most of the tables and fields available for use, see the SiriusSQL Data Dictionary, available from accesso Siriusware Technical Support.

 

Note: In the following table, the AllAdres, AllTrans, BookInfo, Cc_Trans, Printing and Utility tables are local tables only, so are not described in the SiriusSQL Data Dictionary.