All Apps
Menu

Common Errors

Download GDPR

Common Errors

This guide covers the most frequently encountered errors when using the GDPR Data Management app and provides step-by-step solutions.

Installation and Setup Errors

Error: "Cannot install app - compatibility issues"

Symptoms: App installation fails with version compatibility message Causes:

  • BC version too old for app requirements
  • Conflicting AL apps installed
  • Insufficient system resources

Solutions:

  1. Check Version Compatibility:
    • Verify BC version is 26.0+ for latest app version
    • Review Supported Versions
    • Consider upgrading BC or using compatible app version
  2. Check for Conflicts:
    Get-NAVAppInfo -ServerInstance BC260 | Where-Object {$_.Name -like "*GDPR*"}
    • Remove any conflicting GDPR apps
    • Check object ID ranges for conflicts (11195990-11195999)
  3. Verify Resources:
    • Ensure adequate disk space (minimum 100MB)
    • Check available memory (minimum 8GB system RAM)
    • Verify database connection stability

Error: "Permission set creation failed"

Symptoms: GDPR Setup shows empty "Personal Data Permission Set" field Causes:

  • Insufficient user permissions to create permission sets
  • Security filter restrictions
  • Database connection issues

Solutions:

  1. Check User Permissions:
    • User must have SUPER or Security Admin permissions
    • Verify permission to create Permission Sets
    • Check if security filters are blocking creation
  2. Manual Permission Set Creation:
    // Create permission set manually
Permission Set ID: GDPR-PERSONAL-DATA
Name: GDPR Personal Data Access
// Add table data permissions for tables containing personal data
  3. Run Initialization Again:
    • Open GDPR Register List
    • Run Actions > Initialize
    • Monitor for error messages during process

Data Classification Errors

Error: "No elements found during initialization"

Symptoms: GDPR Register List is empty after initialization Causes:

  • Personal Data Permission Set is empty or incorrect
  • User lacks read permissions on system tables
  • Database metadata access issues

Solutions:

  1. Verify Permission Set Configuration:
    // Check GDPR Setup
Table: DD GDPR Setup (11195993)
Field: Personal Data Permission Set
// Should contain valid permission set code
  2. Check Permission Set Contents:
    • Open Permission Sets page
    • Find the personal data permission set
    • Verify it contains table data permissions
    • Add missing table permissions if needed
  3. Re-run Initialization:
    • Clear existing elements: GDPR Documentation Elements table
    • Run initialization process again
    • Monitor progress dialog for specific errors

Error: "Cannot modify documentation element"

Symptoms: Unable to edit or move elements in GDPR Register Causes:

  • Record is locked by another user
  • Insufficient modify permissions
  • Hierarchical constraints prevent modification

Solutions:

  1. Check Record Locks:
    • Verify no other users are editing the same record
    • Close and reopen the page to refresh locks
    • Use BC's "Who's Online" to check concurrent users
  2. Verify Permissions:
    • User needs MODIFY permission on DD GDPR Documentation Element table
    • Check if security filters are restricting access
    • Ensure GDPR-USER or GDPR-ADMIN permission set is assigned
  3. Check Hierarchical Constraints:
    • Cannot create circular references in parent-child relationships
    • Level field must be consistent with hierarchy position
    • Parent Entry No. must reference valid parent element

Data Cleaning Errors

Error: "Access denied during field cleaning"

Symptoms: Cleaning operation fails with "Access denied" errors Causes:

  • Missing table data permissions
  • Field-level security restrictions
  • Record locks preventing modification

Solutions:

  1. Check Table Permissions:
    // User needs these permissions for target tables:
Permission: ReadInsertModifyDelete (RIMD)
Object Type: Table Data
Object ID: [Target Table Number]
  2. Review Security Filters:
    • Check if user security filters restrict access to target records
    • Verify department-based security doesn't block access
    • Consider using GDPR-ADMIN permission set for troubleshooting
  3. Handle Record Locks:
    • Ensure target records aren't locked by business processes
    • Close other BC windows that might lock records
    • Consider scheduling cleaning during off-hours

Error: "Field validation failed during cleaning"

Symptoms: Some fields clean successfully, others fail with validation errors Causes:

  • Business logic prevents clearing certain fields
  • Foreign key constraints require related data
  • Custom validation rules block field clearing

Solutions:

  1. Identify Validation Rules:
    // Check table definition for field validation
Field: [Field Name]
Table Relation: [Related Table]
Validation Code: [Custom Validation]
  2. Handle Foreign Key Dependencies:
    • Clean related records first (child before parent)
    • Use field-specific cleaning approach
    • Consider anonymization instead of clearing
  3. Bypass Validation (Advanced):
    • Use direct database operations for system fields
    • Implement custom cleaning methods for complex validation
    • Contact Q-Team Solutions for app-specific validation issues

Error: "Session timeout during large cleaning operation"

Symptoms: Cleaning stops with timeout error on large datasets Causes:

  • Operation exceeds maximum session duration
  • Database performance issues
  • Insufficient system resources

Solutions:

  1. Optimize Filters:
    • Use more specific filters to reduce record count
    • Process data in smaller batches
    • Clean different tables in separate sessions
  2. Improve Performance:
    -- Check database performance
SELECT TOP 10 * FROM [Company$DD GDPR Table] WHERE [Processing Time] > 1000
-- Review slow operations and optimize
  3. System Tuning:
    • Increase BC service timeout settings
    • Optimize database indexes on filtered fields
    • Schedule cleaning during low-usage periods

Permission and Security Errors

Error: "User cannot access GDPR functions"

Symptoms: GDPR menu items not visible or accessible Causes:

  • GDPR permission sets not assigned
  • Object-level permission restrictions
  • Role Center limitations

Solutions:

  1. Assign Correct Permission Sets:
    Users: [Target User]
Permission Sets: GDPR-USER or GDPR-ADMIN
Company: [Relevant Company] or blank for all companies
  2. Check Object Permissions:
    • Verify execute permissions on GDPR codeunits
    • Check read permissions on GDPR tables
    • Ensure page access permissions are granted
  3. Role Center Configuration:
    • Some Role Centers may not show GDPR actions by default
    • Use Tell Me (Alt+Q) to access GDPR functions directly
    • Consider customizing Role Center to include GDPR actions

Error: "Cannot create session log entries"

Symptoms: Cleaning operations run but no logs are created Causes:

  • Missing insert permissions on log tables
  • Database constraint violations
  • Corrupted log table structure

Solutions:

  1. Verify Log Table Permissions:
    Table: QTEAM Data Cleaner Log Entry (11195990)
Table: QTEAM Cleaner Session Log (11195992)
Required Permission: ReadInsertModify (RIM)
  2. Check Database Integrity:
    • Verify log tables exist and are accessible
    • Check for database constraint violations
    • Review BC error logs for database-specific errors
  3. Reset Log Configuration:
    • Clear existing log entries if corrupted
    • Re-initialize GDPR configuration
    • Test with simple cleaning operation

Performance and System Errors

Error: "Out of memory during initialization"

Symptoms: Initialization process fails with memory errors Causes:

  • Large number of tables with personal data
  • Insufficient system memory
  • Memory leaks in processing logic

Solutions:

  1. System Resource Review:
    • Monitor memory usage during initialization
    • Ensure minimum 16GB RAM for large environments
    • Close unnecessary applications during initialization
  2. Batch Processing:
    • Initialize tables in smaller groups
    • Use custom procedures for very large environments
    • Contact Q-Team Solutions for enterprise-scale deployments
  3. Memory Optimization:
    # Monitor BC service memory usage
Get-Process -Name "Microsoft.Dynamics.Nav.Server" | Select-Object ProcessName, WorkingSet64
# Consider increasing BC service memory allocation

Error: "Database deadlock during cleaning"

Symptoms: Multiple cleaning operations fail with deadlock errors Causes:

  • Concurrent access to same data
  • Lock order conflicts between sessions
  • Database performance issues

Solutions:

  1. Coordinate Sessions:
    • Avoid running multiple cleaning sessions simultaneously
    • Process different table groups in separate time windows
    • Use session scheduling to prevent conflicts
  2. Database Optimization:
    -- Review database locks and blocking
SELECT * FROM sys.dm_tran_locks WHERE resource_type = 'OBJECT'
-- Optimize indexes on frequently accessed tables
  3. Retry Logic:
    • Enable automatic retry for deadlock errors
    • Implement exponential backoff for retry attempts
    • Use smaller batch sizes to reduce lock duration

Integration and API Errors

Error: "Telemetry upload failed"

Symptoms: Application Insights telemetry not working Causes:

  • Internet connectivity issues
  • Application Insights configuration problems
  • Firewall blocking telemetry

Solutions:

  1. Check Connectivity:
    • Verify internet access from BC server
    • Test connection to Application Insights endpoint
    • Review firewall rules for telemetry URLs
  2. Configuration Validation:
    // Verify Application Insights connection string in app.json
"applicationInsightsConnectionString": "InstrumentationKey=..."
  3. Alternative Monitoring:
    • Use BC built-in event logging as backup
    • Implement custom logging if telemetry is blocked
    • Contact Q-Team Solutions for enterprise telemetry solutions

Getting Additional Help

When to Contact Support

  • Errors persist after following troubleshooting steps
  • Custom environment configurations causing issues
  • Performance problems in large-scale deployments
  • Integration issues with other AL apps

Information to Provide

  1. Error Details:
    • Complete error message text
    • BC version and app version
    • Environment type (SaaS/OnPrem)
    • Steps to reproduce the error
  2. System Information:
    • Number of companies and estimated data volume
    • Other installed AL apps
    • Custom modifications or integrations
    • System resource specifications
  3. GDPR Configuration:
    • Screenshot of GDPR Setup page
    • List of assigned permission sets
    • Sample of GDPR Register List showing element structure

Support Channels

Next Steps

For specific error types: