Planning Your Import
Salesmatrix was originally designed to cater for business transactions.
‘Customer A buys Product B from Sales Channel C in Period D’ with values for the sale value, the sale cost and the units of product sold analysed.
This transaction, while wide-ranging, does not cover all aspects of the analysis requirements of all business. Hence, we have designed Salesmatrix to cater to other business transactions. For example:
Client A has Staff Person B perform Work type C in Period D.
Customer A buys a component of Product-Group B from Sales Channel C in Period D.
Customer from Postcode A buys Product B etc.
Or even analysing purchases.
Supplier A provides Product B to Location C in Period D.
The import wizard and the stored scripts provide the ability to change modify the imported data to suit any of the above scenarios and of course any others where there are 4 key dimensions.
The Script files (*.SMD) files are text documents that store the rules for importing data. All dimensions of the import can be modified in these scripts and the details of what the contents are is outlined in the section Using Scripts to Automate Imports
On each of the four data pages in the import wizard is the option check-box ‘Use Custom Script?’ If data fields are entered into the Links screen, clicking this button will display the current SQL select statement that is to be sent to the ODBC driver and then to the accounting software database.
Once the custom scripts entry area is shown and has text in it, this text is not modified until it is cleared completely. If changes have been made to the linking fields, the query must be refreshed by completely deleting the custom query text in the entry area. Recheck the ‘Use Custom Script’ box and the modified custom script will be displayed.
The only limitations to the complexity of the selection statement are the limitations of the particular ODBC driver that is used to query the accounting data. If the driver supports multiple joins and union statements etc., then they can be employed when selecting datasets into Salesmatrix.
Default column names
To enable Salesmatrix to discern where each column of data returned is mapped to, the default script uses an ‘AS’ clause to name the column returned.
The following table lists the AS clause names used by Salesmatrix.
Sales Person/Channel Selection:
What to do if the data doesn’t import?
Once a script has been written or modified, very often there are issues with the data. During the import, you may see a dialogue ‘Errors occurred during Loading. Continue?’ This is a sign that one or more of the four selection scripts did not complete correctly.
Checking the data returned may give some clues as to where the issue lies.
If no value data comes into Salesmatrix there are some steps you can take to check where the issue is.