ServiceNow Power BI Integration Guide

Architecture Overview

Implementation Steps

// Script to create integration user via script
var gr = new GlideRecord('sys_user');
gr.initialize();
gr.user_name = 'powerbi_integration';
gr.first_name = 'Power BI';
gr.last_name = 'Integration';
gr.email = 'powerbi@company.com';
gr.active = true;
gr.password_needs_reset = false;
var userSysId = gr.insert();

// Add roles
var roleGr = new GlideRecord('sys_user_has_role');
roleGr.initialize();
roleGr.user = userSysId;
roleGr.role = 'web_service_admin';
roleGr.insert();

// Widget Client Script for Power BI embed
function($scope, $window) {
  var c = this;
  c.powerBIUrl = 'https://app.powerbi.com/reportEmbed?reportId=your-report-id&autoAuth=true&ctid=your-tenant-id';
  
  c.refreshReport = function() {
    var iframe = document.getElementById('powerbi-frame');
    iframe.src = iframe.src;
  };
}

// Scheduled Script to monitor API usage
var gr = new GlideRecord('sys_rest_message');
gr.addQuery('name', 'CONTAINS', 'powerbi');
gr.addQuery('sys_created_on', '>', gs.daysAgoEnd(1));
gr.query();

var apiCalls = 0;
while (gr.next()) {
  apiCalls++;
}

gs.info('Power BI API calls in last 24 hours: ' + apiCalls);

Common Use Cases

Troubleshooting

Pro Tips

• →Implement a ServiceNow business rule to automatically trigger Power BI refresh webhooks when critical data changes occur, providing near real-time dashboard updates without waiting for scheduled refresh cycles. Create a custom REST endpoint that accepts Power BI refresh triggers and use the Microsoft Power BI REST API to programmatically refresh specific datasets when ServiceNow records are modified.
• →Leverage ServiceNow's sysparm_fields parameter in OData queries to only retrieve necessary columns, significantly improving refresh performance and reducing API call overhead. This is especially important for tables with many columns like cmdb_ci or incident where you typically only need 10-15 fields for dashboard visualization.
• →Create a ServiceNow update set specifically for Power BI integration components including custom roles, ACLs, and Scripted REST APIs to ensure consistent deployment across development, test, and production instances. Document all Power BI-specific ServiceNow configurations to streamline troubleshooting and knowledge transfer to other team members.
• →Use Power BI's dataflow feature to create reusable data preparation logic that multiple dashboards can consume, centralizing ServiceNow data transformations and reducing redundant API calls to your ServiceNow instance. This approach also enables better change management when ServiceNow table structures evolve.
• →Implement custom logging in ServiceNow to track Power BI API usage patterns and identify opportunities for optimization, such as creating summary tables for frequently accessed aggregated data or implementing caching strategies for reference data that changes infrequently. Monitor the sys_rest_message table to understand API call volumes and timing patterns.
• →Configure Power BI row-level security (RLS) to automatically filter ServiceNow data based on user attributes like department or assignment group, ensuring users only see relevant data while maintaining a single shared dashboard. Map ServiceNow user roles to Power BI security roles for seamless access control integration.

Known Limitations

• —ServiceNow REST API rate limits restrict Power BI refresh operations to 5,000 API calls per hour per user, which can be problematic for large datasets or multiple concurrent dashboards refreshing simultaneously. Organizations with extensive ServiceNow data may need to implement data partitioning strategies or consider upgrading to ServiceNow Performance Analytics for better BI integration capabilities.
• —Power BI's maximum dataset size limitations (1GB for Power BI Pro, 10GB for Premium) can be quickly exceeded when importing large ServiceNow tables like audit logs, journal entries, or historical incident data spanning multiple years. Real-time streaming datasets are limited to 1 million rows per hour, which may not accommodate high-volume ServiceNow instances during peak activity periods.
• —The uni-directional nature of the integration means Power BI cannot write data back to ServiceNow, limiting use cases to reporting and analytics rather than operational workflows. Users cannot create or update ServiceNow records directly from Power BI dashboards, requiring separate integration approaches for bidirectional scenarios that need workflow capabilities.
• —ServiceNow's OData implementation has limited support for complex joins and aggregations, often requiring multiple API calls or data transformation in Power BI to achieve sophisticated reporting requirements. Complex ServiceNow table relationships may need to be flattened or pre-processed through custom Scripted REST APIs to optimize Power BI consumption.
• —Authentication token management can become complex in enterprise environments, especially when using OAuth 2.0 flows with Power BI Service's scheduled refresh capabilities. Token expiration and renewal processes may require manual intervention or custom automation to maintain uninterrupted dashboard refresh operations in production environments.

Frequently Asked Questions