Skip to content

Troubleshooting

Common issues and solutions for the Compliance Dashboard.

Data Issues

No Data Showing in Dashboard

Symptoms: - All visuals show blank or zero - "No data" message on report pages

Solutions:

  1. Verify Dataverse Connection 

    Power BI Desktop > Transform Data > Data source settings
Verify Dataverse URL is correct

  2. Check Data Exists in Dataverse

  3. Open Power Apps > Tables
  4. Verify fsi_controlmaster row count matches your loaded control inventory (62 sample / 78 baseline)

  5. Verify fsi_controlassessment has assessment records

  6. Refresh Dataset

  7. Click Refresh in Power BI Desktop

  8. Check for errors in refresh dialog

  9. Verify Authentication

  10. Re-enter credentials if prompted
  11. Ensure account has Dataverse read permissions

Stale Data

Symptoms: - Dashboard shows old data - Score date is outdated

Solutions:

  1. Manual Refresh
  2. In Power BI Service: Dataset > Refresh now

  3. In Power BI Desktop: Home > Refresh

  4. Check Scheduled Refresh

  5. Power BI Service > Dataset > Settings > Scheduled refresh

  6. Verify refresh is enabled and scheduled

  7. Verify Flow Execution

  8. Power Automate > CD-ScoreCalculator
  9. Check last run status and time

Missing Controls

Symptoms: - Fewer controls displayed than expected - Specific controls missing from list

Solutions:

  1. Load Control Master Data 
    python scripts/load_sample_data.py --controls-only

  2. Confirm the control master source matches your inventory before rerunning the loader (62 sample / 78 baseline)

  3. Verify Control Master Table

  4. Check fsi_controlmaster row count

  5. Ensure all expected controls present (62 sample / 78 baseline)

  6. Check Filter Context

  7. Clear all slicers
  8. Remove any report-level filters

Performance Issues

Slow Dashboard Loading

Symptoms: - Report takes >10 seconds to load - Visuals load sequentially

Solutions:

  1. Reduce Data Volume
  2. Filter to recent 90 days instead of all history

  3. Use aggregated tables for trends

  4. Optimize Measures

  5. Replace calculated columns with measures

  6. Use variables in complex DAX

  7. Enable Query Caching

  8. Power BI Service > Dataset > Settings

  9. Enable "Enhanced compute engine"

  10. Use Import Mode

  11. If using DirectQuery, switch to Import
  12. Schedule regular refresh instead

Slow Refresh

Symptoms: - Data refresh takes >15 minutes - Timeout errors during refresh

Solutions:

  1. Incremental Refresh
  2. Configure incremental refresh for large tables

  3. Only refresh recent data

  4. Reduce Query Complexity

  5. Review Power Query transformations

  6. Move complex logic to Dataverse

  7. Gateway Performance (if applicable)

  8. Upgrade gateway hardware
  9. Configure connection pooling

Flow Issues

Score Calculator Flow Fails

Symptoms: - No new score records created - Flow shows failed status

Error: "Dataverse connection failed" 

Solution:
1. Open flow in edit mode
2. Expand failed action
3. Re-authenticate Dataverse connection
4. Save and test

Error: "Invalid filter expression" 

Solution:
1. Verify filter syntax in List rows action
2. Check column names match schema
3. Update filter if schema changed

Error: "Timeout expired" 

Solution:
1. Increase timeout in flow settings
2. Add pagination to List rows
3. Process in batches

Exception Monitor Flow Fails

Symptoms: - SLA status not updating - No alert notifications sent

Error: "User not found" 

Solution:
1. Verify exception owner lookup is valid
2. Check user exists in environment
3. Update orphaned ownership records

Error: "Teams notification failed" 

Solution:
1. Verify the Microsoft Teams connection reference is valid (the solution uses the
   shared_teams connector with PostMessageToConversation, not incoming webhooks)
2. Re-authenticate the Teams connection in Power Automate > Connections
3. Check that the recipient user has a Teams license and mailbox
4. Verify the Flow bot is not blocked by the recipient

Authentication Issues

"Access Denied" Error

Symptoms: - Cannot connect to Dataverse - 403 error in Power BI

Solutions:

  1. Verify User Permissions
  2. Check user has CD Viewer security role

  3. Verify environment access

  4. Check Service Principal

  5. Verify app registration is active
  6. Check client secret hasn't expired

  7. Confirm API permissions granted

  8. Conditional Access

  9. Check if CA policy blocks access
  10. Verify location/device compliance

"Token Expired" Error

Symptoms: - Refresh fails with authentication error - Interactive sign-in required

Solutions:

  1. Re-authenticate
  2. Power BI Service > Dataset > Settings
  3. Click "Edit credentials"

  4. Sign in again

  5. Service Principal Refresh

  6. Check client secret expiration
  7. Rotate secret if expired
  8. Update connection credentials

Visual Issues

Incorrect Calculations

Symptoms: - Score doesn't match expected value - Percentages don't add to 100%

Solutions:

  1. Verify Measure Logic
  2. Review DAX measure definitions

  3. Test with known data

  4. Check Filter Context

  5. Verify slicer selections

  6. Check cross-filtering behavior

  7. Validate Source Data

  8. Export data to Excel
  9. Manually verify calculations

Formatting Issues

Symptoms: - Colors not displaying correctly - Conditional formatting not working

Solutions:

  1. Verify Color Measures
  2. Check color measure returns valid hex codes

  3. Test measure in card visual

  4. Apply Formatting Correctly

  5. Format pane > Conditional formatting

  6. Select correct measure for "Field value"

  7. Check Visual Settings

  8. Reset visual to defaults
  9. Re-apply formatting rules

Deployment Issues

Solution Import Fails

Symptoms: - Error during Dataverse solution import - Missing dependencies error

Solutions:

  1. Check Dependencies
  2. Verify prerequisite solutions installed

  3. Check version compatibility

  4. Import in Correct Order

  5. Import base tables first
  6. Then import flows

  7. Finally import dashboard

  8. Environment Capacity

  9. Check Dataverse storage available
  10. Remove old data if needed

Publish to Power BI Fails

Symptoms: - Error during report publish - Workspace not found

Solutions:

  1. Verify Workspace Access
  2. Check user has Contributor or higher role

  3. Verify workspace exists

  4. Check License

  5. Confirm Power BI Pro license assigned

  6. For Premium workspace, verify capacity

  7. Network Issues

  8. Check proxy/firewall settings
  9. Verify Power BI endpoints accessible

Recovery Procedures

Rebuild Score History

If score history is corrupted or missing, manually trigger the CD-ScoreCalculator flow for each date or re-run assessments:

# Reload control master data and regenerate sample scores
python scripts/load_sample_data.py --export --force

Reset Exception SLA Status

If SLA calculations are incorrect, manually trigger the CD-ExceptionMonitor flow:

# Trigger the CD-ExceptionMonitor flow manually from Power Automate
# Navigate to: Power Automate > CD-ExceptionMonitor > Test > Manually

Restore Control Master

If control master data is corrupted:

# Reload control master from reference
python scripts/load_sample_data.py --controls-only --force

Support

For issues not covered here:

  1. Check FSI-AgentGov-Solutions Issues
  2. Review flow run history for detailed errors
  3. Check Power BI Service activity log
  4. Contact your Power Platform administrator

Compliance Dashboard v1.0.3