Breadcrumbs

Troubleshooting Team member configuration

This section provides comprehensive troubleshooting guidance for common Team Members issues in Business Central 25 with Muncipal manager.

Common Issues and Solutions

1. User Cannot See Expected Data in Account Budget Overview

Symptoms:

  • Page loads but shows no data or limited data

  • User reports missing accounts or incomplete information

  • Filtered view appears empty

Root Causes and Solutions:

Municipal Dimension Filter Issues:

  • Check: User's Global Dimension 1 Filter assignment

  • Solution: Verify municipal dimension assignment in user permission sets

  • Verification: Test with SUPER user to confirm municipal data exists

Activity-Based Filtering:
The page automatically filters to show only accounts with activity:

// Only shows accounts with activity
if Rec."Net Change" <> 0 then
    Rec.Mark(true)
else begin
    Rec.CalcFields("Budgeted Amount");
    if Rec."Budgeted Amount" <> 0 then
        Rec.Mark(true);

Troubleshooting Steps:

  1. Check if accounts have Net Change ≠ 0

  2. Verify accounts have Budgeted Amount ≠ 0

  3. Confirm accounts have Balance at Date ≠ 0

  4. Review municipality dimension filter effectiveness

  5. Temporarily disable MarkedOnly filter for testing

Solution:

  • Ensure data exists in the filtered scope

  • Verify dimension filters are correctly configured

  • Check date filters and period settings

2. "You Do Not Have Permission" Errors

Symptoms:

  • Access denied when opening pages

  • Cannot execute specific actions

  • Error messages about insufficient permissions

Account Budget Overview Specific Checks:

  • Table Data 15 (G/L Account) - Read permission required

  • Page 10008094 (Sve Account Budget Overview) - Execute permission required

  • Municipal dimension access - Verify field class permissions

Troubleshooting Process:

Step 1: Identify the Error

  • Note exact error message

  • Identify which object/page is being accessed

  • Check if error relates to specific fields or actions

Step 2: Verify License Type

  • Confirm user has Team Member license assigned

  • Check license limitations in Microsoft 365 admin center

  • Review Application Area assignments (Basic vs Suite)

Step 3: Check Permission Sets

Required Permission Sets:
- TEAM MEMBER
- D365 TEAM MEMBER  
- D365 READ

Optional (based on role):
- D365 APPROVAL WORKFLOWS
- TIMESHEET

Step 4: Test with Elevated Permissions

  • Temporarily assign broader permissions

  • Identify minimum required permissions

  • Document specific objects needed

3. Empty Account Budget Overview Page

Specific Troubleshooting:

Data Availability Check:

// Verify accounts exist with activity
G/L Account.SetFilter("Net Change", '<>0');
G/L Account.SetFilter("Budgeted Amount", '<>0');

Municipal Dimension Verification:

// Check applied dimension filters
FilterGroup(8); // System filters
GetFilter("Global Dimension 1 Filter");

Municipality Access Testing:

  • Verify MunicipalityDimMgt.FindDim1Filter('FIN', '') returns expected values

  • Check 'FIN' parameter relevance to user's setup

  • Confirm dimension codes are properly assigned

Solution Steps:

  1. Check Data Scope: Ensure accounts exist within the user's municipal scope

  2. Verify Filters: Review all applied filters (date, dimension, activity)

  3. Test Dimension Access: Confirm municipal dimension assignments

  4. Performance Check: Monitor page loading times and data volume

4. Icelandic Language Display Problems

Symptoms:

  • Missing Icelandic translations

  • Mixed language display

  • Incorrect character encoding

Troubleshooting:

User Language Settings:

  • Verify user's language setting in Business Central profile

  • Check Language ID field: should be is-IS for Icelandic

  • Confirm Locale ID matches regional preferences

System Configuration:

  • Ensure Icelandic language pack is installed

  • Verify ISL comment translations in page captions

  • Check field caption translations

Code-Level Verification:

// Check for Icelandic translations
Caption = 'Account Budget Overview', Comment = 'ISL = Yfirlit fjárhagsreikninga - Áætlun';
Caption = 'Difference', Comment = 'ISL = Mismunur';

Solutions:

  1. Install Language Pack: Ensure Icelandic localization is properly installed

  2. User Profile: Set correct language preferences

  3. System Settings: Verify regional settings and character encoding

5. Performance Issues

Symptoms:

  • Slow page loading

  • Timeouts when opening Account Budget Overview

  • System unresponsiveness

Performance Analysis:

Data Volume Issues:

  • Check number of accounts in municipal scope

  • Verify filtering effectiveness

  • Monitor concurrent user load

Dimension Filter Efficiency:

// Efficient filtering at system level
Rec.FilterGroup(8);
Rec.SetFilter("Global Dimension 1 Filter", DimFilter);
Rec.FilterGroup(0);

Optimization Solutions:

  1. Improve Filtering: Ensure dimension filters are applied at system level

  2. Data Reduction: Use MarkedOnly to show only relevant accounts

  3. Page Optimization: Review field calculations and visibility settings

  4. Network Check: Verify network connectivity and bandwidth

6. Workflow Approval Issues

Symptoms:

  • Cannot see approval requests

  • Approval actions not working

  • Workflow notifications not received

Permission Requirements:

  • D365 APPROVAL WORKFLOWS permission set required

  • WORKFLOW APPROVAL permissions for specific workflows

  • Email notification setup required

Troubleshooting Steps:

  1. Check Permission Sets: Verify workflow permissions are assigned

  2. Workflow Configuration: Ensure workflows are properly configured

  3. Email Setup: Verify email configuration for notifications

  4. User Assignment: Confirm user is assigned to appropriate approval groups

Implementation-Specific Debugging

Account Budget Overview Debug Process

Step 1: Verify Page Access

Check: Can user open page 10008094?
Expected: Page opens without permission errors
Action: If blocked, check permission sets

Step 2: Check Data Filtering

Check: Are municipal filters applied correctly?
Expected: Data filtered to user's municipality
Action: Verify FilterGroup(8) dimension filters

Step 3: Test Data Visibility

Check: Are accounts with activity visible?
Expected: Accounts with Net Change or Budget visible
Action: Verify marking logic and data calculation

Step 4: Validate Field Access

Check: Are visible fields displaying correctly?
Expected: Financial data visible, admin fields hidden
Action: Check field visibility settings and Application Areas

Municipal System Debugging

Municipal Dimension Access:

  1. Verify Dimension Setup: Check municipal dimension configuration

  2. Test Filter Logic: Validate MunicipalityDimMgt.FindDim1Filter results

  3. Check Assignments: Confirm user dimension assignments

  4. Test Boundaries: Verify users cannot access other municipal data

Field Class Validation:

  1. Check Enum Values: Confirm Income/Balance enum values are properly set

  2. Verify Filtering: Test IncomeBalanceFilter enum application

  3. Access Control: Ensure field class VAT setup is hidden from Team Members

Diagnostic Tools and Techniques

1. Permission Analysis

Built-in Tools:

  • Permission Sets page: Review assigned permissions

  • Effective Permissions: Analyze combined permission effects

  • Permission Conflicts: Identify conflicting permissions

Custom Analysis:

// Check specific table permissions
if not HasPermission(TableData, DATABASE::"G/L Account") then
    Error('No access to G/L Account table');

2. Data Access Testing

Manual Testing:

  • Log in as the specific user

  • Navigate through typical user workflows

  • Test both successful and restricted operations

  • Document any unexpected behavior

Automated Testing:

  • Create test scripts for common scenarios

  • Verify data filtering works correctly

  • Test permission boundaries

  • Monitor performance metrics

3. Logging and Monitoring

Enable Comprehensive Logging:

  • User access attempts

  • Permission errors

  • Data access patterns

  • Performance metrics

Log Analysis:

  • Review error patterns

  • Identify common issues

  • Monitor user behavior

  • Track system performance

Escalation Procedures

Level 1: Basic Troubleshooting

Administrator Actions:

  1. Verify Setup: Check user configuration and permissions

  2. Test Access: Reproduce the issue

  3. Check Documentation: Review setup documentation

  4. Simple Fixes: Apply common solutions

Level 2: Advanced Troubleshooting

Technical Analysis:

  1. Deep Dive: Analyze system logs and configuration

  2. Code Review: Check custom configurations and modifications

  3. Performance Analysis: Monitor system performance and optimization

  4. Coordination: Work with technical teams

Level 3: Expert Support

When to Escalate:

  • Complex permission issues

  • System-wide performance problems

  • Integration failures

  • Data corruption concerns

Escalation Information:

  • User details and configuration

  • Exact error messages

  • Steps to reproduce

  • System environment details

  • Attempted solutions

Prevention Strategies

1. Proactive Monitoring

Regular Checks:

  • Weekly: Review user access logs for errors

  • Monthly: Analyze performance metrics

  • Quarterly: Conduct permission audits

  • Annually: Review and update procedures

2. Documentation Maintenance

Keep Current:

  • User Guides: Update with new features

  • Troubleshooting: Add new solutions as discovered

  • Configuration: Document all customizations

  • Procedures: Update troubleshooting workflows

3. Training and Communication

User Education:

  • Regular Training: Keep users informed of limitations

  • Clear Communication: Explain what Team Members can/cannot do

  • Support Channels: Provide clear support procedures

  • Feedback Loop: Collect and act on user feedback

Quick Reference Troubleshooting

Common Error Messages

"You do not have permission to..."

  • Check: Permission sets assigned

  • Verify: License type is correct

  • Test: With elevated permissions

"No records found"

  • Check: Dimension filters

  • Verify: Data exists in scope

  • Test: With broader filters

"Page cannot be displayed"

  • Check: Page permissions

  • Verify: Application Area assignments

  • Test: Page accessibility

Emergency Procedures

Critical Access Issues:

  1. Immediate: Assign SUPER permissions temporarily

  2. Identify: Root cause of access failure

  3. Resolve: Apply appropriate permanent solution

  4. Document: Issue and resolution for future reference

System-Wide Issues:

  1. Assess: Scope of the problem

  2. Communicate: Notify affected users

  3. Isolate: Identify problematic components

  4. Resolve: Apply fixes systematically

  5. Monitor: Verify resolution effectiveness