Power BI
Custom integration — assessment requiredAgree the dataset before designing the dashboard.
Explore data & scopeSupported file workflows include product CSV preview/import and configured target uploads. Some daily XLSX workflows are restricted to specific enabled deployments. A spreadsheet extension alone does not make a file compatible.
Record ownership and direction are defined below. No universal two-way sync is implied.
Column names and identifiers must match the selected workflow.
A duplicate product code should not silently create a second product.
Rejected rows need correction before the next upload.
Each row is a separate scope decision. Supported workflows still require configuration; proposed records require assessment and implementation.
| Record or object | Direction | System of record | Purpose | Availability / prerequisites |
|---|---|---|---|---|
| Product catalogue CSV | File → SalesTOS | Agreed product master | Product creation or updates | Supported product template and manage permission |
| Target CSV | File → SalesTOS | Approved target source | Enabled target workflow | Supported in configured target upload |
| Daily XLSX data | File → SalesTOS | Agreed source | Specific daily-data workflow | Deployment-restricted; not general Enterprise entitlement |
| Customer or receivables files | File → SalesTOS | Agreed source system | Candidate migration or balance feed | Sample and enabled importer assessment required |
Use the exact template for the enabled workflow. Product imports support preview and row validation, with up to 5,000 rows per submission. Matching product codes can update existing products. Different importers have different duplicate and transaction rules; do not generalise one importer’s behaviour to all spreadsheets.
An authorised manager previews a product CSV, corrects invalid rows and imports the accepted catalogue changes. The result identifies row errors; the manager reviews the result before retrying rejected data.
Importing a file changes the selected SalesTOS records. It does not update the originating ERP or accounting workbook automatically.
Use an authorised setup process for credentials. The enquiry form does not request passwords or API secrets.
Product imports validate rows and match existing product codes within the tenant; a submission may contain partial successes. Restricted daily upload workflows have separate batch and duplicate controls. Inspect the actual result before retrying to avoid unintended updates.
No. Each workflow expects a specific format and mapping.
The supported product importer matches existing tenant product codes for updates; review the preview and result.
Yes, product imports may report accepted rows alongside row errors. Retry only after reviewing the outcome.
No. Those workflows are enabled only in specific deployments and require scope confirmation.
Selected enabled import workflow and current template; Stable record codes and sample rows; Authorised user with required manage access; Backup/review approach and correction owner. Share redacted examples through an agreed channel, never passwords or API secrets in the public form.
Review the objects and prerequisites on this page, then agree mapping, access, refresh timing and acceptance criteria. Importing a file changes the selected SalesTOS records. It does not update the originating ERP or accounting workbook automatically.
No matching questions. Clear your search or discuss your requirements with us.
Agree the dataset before designing the dashboard.
Explore data & scopeConnect employee identity and attendance events.
Explore data & scopeDefine one useful interface between your system and field work.
Explore data & scopeBring your business workflow and current setup. We’ll use them to assess the right data scope.