Excel & CSV
File import supportedStart with an approved template and a reviewable import.
Explore data & scopeAssess authorised SalesTOS operational data for Power BI reporting. Define metrics, ownership and refresh needs first. A native SalesTOS Power BI connector, embedded licence or real-time dataset is not currently verified.
Record ownership and direction are defined below. No universal two-way sync is implied.
Reports need consistent definitions of activity, sales and collections.
Refresh cut-offs can explain differences between dashboards.
Data access must remain limited to the approved audience.
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 |
|---|---|---|---|---|
| Operational measures | SalesTOS → reporting dataset | SalesTOS | Candidate management analysis | Assessment: enabled exports or custom feed |
| Team and customer dimensions | SalesTOS → reporting dataset | Agreed master | Reporting context | Assessment: authorised fields and identifiers |
| Refresh timestamp | Feed → report | Feed process | Explain data freshness | Required in proposed dataset design |
| Report edits | No writeback proposed | Power BI report | Analysis only | No operational update flow promised |
Power BI supports multiple data sources. Select a supported export or a separately implemented feed after inspecting available SalesTOS data and access rules. Do not assume direct database access, embedded dashboards or automatic row-level security.
A management report could combine an approved monthly activity dataset with office targets. The report displays its refresh cut-off and metric definitions so managers can understand differences from operational views.
Filtering or editing a report does not update SalesTOS records or the accounting system.
Use an authorised setup process for credentials. The enquiry form does not request passwords or API secrets.
Agree reconciliation totals, failed-refresh alerts and access enforcement. These reporting controls require implementation and validation; they are not delivered by a connector listing.
No verified native connector is offered on this page.
Refresh depends on the agreed source and feed; no real-time commitment is made.
Licensing and embedding requirements must be confirmed separately.
Not automatically. Data access must be designed and tested for the reporting environment.
Required measures and their definitions; Approved report audience and data scope; Refresh frequency and available export formats; Power BI environment, licensing and report 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. Filtering or editing a report does not update SalesTOS records or the accounting system.
No matching questions. Clear your search or discuss your requirements with us.
Start with an approved template and a reviewable import.
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.