Steps for Exporting
To export historical reporting data, perform the following steps.
- Log into the Stratus UI either via Website or the Teams Personal App
Locate the sidebar and click on "Reporting"Reporting Section
Locate the CSV Export area in the Reporting panel and click on the time period (4 month) button
The duration is hard-set and includes the last 3 months plus the current ongoing.
→ A CSV file is generated and downloaded. Filename is "CsvExport4Months_Validation_Service_-_IVR_Selection_YYYY-MM-DDThh_mm_ss.csv"CSV Export area
- You may now import the file into any evaluation tool: Import Data > Text / CSV
Data fields of the CSV are comma-separated
What's part of the CSV File
|TaskType||Describes the Type of Task, like Inbound Service|
Describes the first involved TeamMember
|LastAcceptedTeamMemberDisplayName||Describes the last involved TeamMember|
|OriginType||Conversation OriginType from which conversation originated|
|AcceptTimeMs||Duration between the moments when the system detects a new task and the task is accepted by the system or terminated|
|StartedDate||The date on which the task took place|
|StartedYear||The year on which the task took place|
|StartedQuarter||The quarter on which the task took place|
|StartedMonthNumber||The Month in Number on which the task took place|
|StartedDayOfMonth||The Day in Number on which the task took place|
|StartedWeekNumber||The Week in Number on which the task took place|
|StartedHourOfDay||The Hour of the Day on which the task took place|
|TaskDirection||Indicates the direction (Inbound or Outbound) of the Task|
|TaskId||Provides a unique Id of the Task and Service|
|TaskResult||After the Call is Hung-up and Terminated or Lost, the Task gets an End Result|
|IsInOpeningHour||According to the Calendar, we indicate if the the Task took place In or Out of opening hours|
|IsQueued||Indicates if the Task was queued|
|IsStandbyDuty||Indicates if the Task took place within the StandByDuty|
|TeamService||Indicates which team handled the Task|
|StartedMonth||The Month in Name on which the task took place|
|StartedWeekDay||The Day in Name on which the task took place|
|AgentSelectionAlgorithmType||Indicates the Algorithm on how the Task was provided to an agent|
|StartedTime||The Time on which the task took place|
|CallerSip||The SIP who called the Service|
|InitiallyCalledSip||The SIP of the Target which was first called|
|HangUpType||Indicates who hanged up the call (Customer or Agent)|
|PrimaryModality||Indicates what was the latest Modality recorded to this Task|
|InitialModality||Indicates the initial Modality when the Task was registered in the System|
|CalendarCategoryType||Indicates what Calendar Type was set in the Calendar|
|TransferType||Indicates who and how the Task was transferred|
|TaskResultGroup||Clusters the Task Result into a specific Group|
|QueueTime(T)_HHMMSS||Duration in "HH:MM:SS" Format, both for an individual task and for, as an average value, across all tasks|
|IvrTime(T)_HHMMSS||Duration in "HH:MM:SS" Format, both for an individual task and for, as an average value, across all tasks|
|ConnectedTime(T)_HHMMSS||Duration in "HH:MM:SS" Format, both for an individual task and for, as an average value, across all tasks|
Import in Power BI
Define a local folder location where your CSV export will be stored in future. Preferably this location should not change thereafter since Power BI uses persistent source file paths.
To import and display the Stratus Team CSV export within your Power BI templates, perform the following steps:
First BI Report Startup
- Copy the BI Template (.pbix) and CSV export into your prepared folder
- Open the Power BI template file → Dummy data will be loaded as a default to showcase the various graphs
- On "Home" Ribbon > Click "Transform Data" → An error for the persistent CSV path might be shown, this is expected
- On "Query Settings" sidebar click on "Source" → Warning button changes to "Edit Settings"
- Click "Edit Settings" → A "file path" dialogue opens.
- Adapt path to the new static CSV path you prepared in preconditions.
- Click "OK" → Data should now be retrieved and shown in the preview.
- Click "Close & Apply" → BI Should now refresh with the ne CSV data and update the graphs accordingly.
In future you just need to replace the CSV file and open the BI report and the data should automatically refresh.
At this point you are done. When you want to append further CSV data, read the next step.
Identify and append future CSV Data via "TaskID"
Note that future BI reports will not be automatically appended when you replace the source CSV file - previous CSV data will always be discarded by BI. A very likely user requirement at this point might be that you want to keep existing CSV data values and append new reports, or otherwise disregard data that is not meaningful.
By using the unique identifier "TaskID" you can adapt the report to your needs.
- Open your existing CSV file (e.g. an export from 2 months ago) in any tool that can edit CSV files (e.g. Excel)
Note the "Task ID" column and the last entry written at the bottom of the CSVTaskID as unique identifier for data entries
- Simply open the newly downloaded CSV file you want to append to your existing report
- Find the "TaskID" column and copy every new entry downwards from there on.
- Paste the new rows at the bottom of your existing CSV export and save.
- Open your existing BI Report which should now refresh and include all newly appended data.