Jump to content

NCR - DataCair Tickets: Difference between revisions

From PBI Reporting Wiki
Line 26: Line 26:
!Transformations
!Transformations
|-
|-
|Example Query
|Datacair tickects table API link =<nowiki>https://customer-service.datacair.com/api/ticket/ticket?department=4&limit=1000000000</nowiki>
|
* '''API Endpoint''': <code><nowiki>https://customer-service.datacair.com/api/ticket/ticket?department=4&limit=1000000000</nowiki></code>
 
* '''Purpose''': Retrieves comprehensive ticket information for department ID '''4''', including metadata and key lifecycle fields. The <code>limit</code> parameter is explicitly set to a very high value to ensure all relevant records are returned in a single call, bypassing default pagination limits.
|
|
Example transformations
Example transformations

Revision as of 10:09, 30 January 2026

Summary

This Power BI report provides a centralized view of service ticket performance across entities. Its API-sourced data has calculated metrics, and user-interactive filters to enable monitoring of resolution efficiency.

Filters

Filter Description
Date picker Allows users to filter the dataset by a specific date or date range.
Entity slicer Enables users to filter the report by entity ( Business unit)
Region slicer Enables users to filter the report by region

Data Transformation Applied

Query Transformations
Datacair tickects table API link =https://customer-service.datacair.com/api/ticket/ticket?department=4&limit=1000000000
  • API Endpoint: https://customer-service.datacair.com/api/ticket/ticket?department=4&limit=1000000000
  • Purpose: Retrieves comprehensive ticket information for department ID 4, including metadata and key lifecycle fields. The limit parameter is explicitly set to a very high value to ensure all relevant records are returned in a single call, bypassing default pagination limits.

Example transformations

Calculations

Columns Calculation Description
Example Example calc Example description