Reference

Overview

This reference section provides detailed technical information about BRC Connect’s structure, permissions, and components.

Permission Sets

BRC CONNECT - EDIT

Purpose: Full access to configure and use BRC Connect

Assigned To: Integration administrators, operations managers

Permissions Granted:

Key Pages Accessible:

• BRC Connect Setup
• BRC Connect Entries
• BRC Connect Content
• BRC Connect Type
• BRC Content Type Field Setup
• BRC Mapping
• BRC Outgoing Sync Queue
• BRC Connect Error List

BRC CONNECT - VIEW

Purpose: Read-only access for monitoring and support

Assigned To: Support staff, analysts, auditors

Permissions Granted:

Limitations:

• Cannot modify configuration
• Cannot create/update/delete records
• Cannot run processing actions
• Can view entries, content, errors

Additional BC Permissions Required

Users also need standard BC permissions based on their role:

For Order Processing:

• Sales Order management (Tables 36, 37)
• Customer management (Table 18)
• Item management (Table 27)

For Inventory Sync:

• Item Ledger Entry read (Table 32)
• Inventory posting (Item Journals)

For Payment Processing:

• Gen. Journal Line management (Table 81)
• Payment Journal posting

Database Schema

Core Tables

BRC Connect Entry (12073500)

Purpose: HTTP request/response log

Key Fields:

Indexes:

• Primary Key: Entry No.
• Status: For filtering by processing status
• Entry DateTime: For date-based queries
• BRC Connect Type, Source: For type-specific queries

BRC Connect Setup (12073501)

Purpose: Global configuration

Key Fields:

Configuration Categories:

1. Connection Settings (API Path, Bearer Token, etc.)
2. Automation Flags (Auto Download, Auto Create, etc.)
3. Processing Limits (Max Count, Retries)
4. Document Settings (Payment, Totals, VAT)
5. Inventory Settings (Inventory Type, Locations)
6. Monitoring (Email alerts, logging)

BRC Connect Content (12073502)

Purpose: Parsed JSON documents

Key Fields:

Indexes:

• Primary Key: BRC Connect Type, BRC Connect ID
• Processing: Status, BRC Connect Type (optimized for processing queries)
• ProcessingByType: BRC Connect Type, Status (type-specific queries)
• Parent: Parent Type, Parent ID (hierarchical navigation)
• QueuedCreate: Status, Created Date (batch processing)

BRC Connect Value (12073504)

Purpose: Key-value pairs extracted from JSON

Key Fields:

Use Cases:

• Field-level validation
• Custom field extraction
• Extended info mapping
• Audit trail for data changes

BRC Connect Type (12073503)

Purpose: Entity type configuration

Key Fields:

Standard Types:

• DOCUMENT (Sales documents)
• CUSTOMER (Customers)
• ITEM (Items)
• INVENTORY (Stock levels)
• PRICE (Sales prices)
• PAYMENT (Payments)
• SHIPMENT (Shipments)
• INVOICE (Invoices)
• CREDITMEMO (Credit memos)

BRC Content Type Field Setup (12073505)

Purpose: JSON to BC field mapping

Key Fields:

JSON Path Examples:

• buyer.email - Nested object
• lines[0].itemNo - Array element
• totals.grandTotal - Nested value

BRC Mapping (12073507)

Purpose: Value translation

Key Fields:

Common Mappings:

• Payment methods: “credit_card” → “CC”
• Document types: “pending” → “Order”
• Statuses: “completed” → “Invoice”

BRC Outgoing Synce Queue (12073511)

Purpose: Outbound synchronization queue

Key Fields:

Processing:

• Job queue processes queue every N minutes
• Records marked Synced = TRUE after success
• Error Count increments on failure
• Retry logic based on error type

Codeunit Reference

Core Processing Codeunits

Document Processing Codeunits

Customer/Item Management Codeunits

Outbound Sync Codeunits

Validation Codeunits

Enum Reference

BRC Content Status

Values:

• New (0): Downloaded, not yet parsed
• Read (1): Parsed into values
• Validated (2): Passed validation
• OK (3): BC record created successfully
• Error (4): Processing failed

BRC Process Run Status

Values:

• Queued (0): Entry created, not sent
• Not Sent (1): Ready to send
• Sent and Received (2): Response received
• Finished (3): Processing complete
• Error (4): HTTP or processing error

BRC Service Type

Values:

• Get All (0): Batch download
• Get (1): Single record fetch
• Create (2): Create new record
• Update (3): Update existing record
• Delete (4): Delete record

BRC Document Type

Values:

• Order (0): Sales Order
• Invoice (1): Sales Invoice
• Credit Memo (2): Sales Credit Memo
• Blanket Order (3): Sales Blanket Order
• Return Order (4): Sales Return Order
• Quote (5): Sales Quote
• Purchase Order (6): Purchase Order

BRC Payment Option

Values:

• One Payment (0): Single payment line
• Multiple Payments (1): One line per payment method
• Add Payment Lines (2): Payments as sales lines
• Ignore Payments (3): Don’t process payments

BRC Inventory Type

Values:

• Real-time (0): Current on-hand
• Available (1): Projected available
• Grouped by Location (2): Separate by warehouse
• Outstanding (3): On purchase orders

Page Reference

Configuration Pages

Operational Pages

Supporting Pages

API Endpoints (External System)

Required Inbound Endpoints

External systems must provide these endpoints:

Required Outbound Endpoints

BRC Connect sends to these endpoints:

Authentication

Header:

Authorization: Bearer {token}

Token Configuration:

• Stored in BRC Connect Setup
• Encrypted in database
• Sent with every HTTP request

Version History

Version 25.0.25051.1 (Current)

Release Date: 2025 (Build 25051)

Platform Requirements:

• Business Central 25.0+
• AL Runtime 12.0
• Cloud only

Key Features:

• Bidirectional integration with e-commerce/POS
• Automated order processing pipeline
• Real-time inventory synchronization
• Payment processing integration
• Two-pass identity matching optimization
• Parallel processing support
• Event-driven outbound sync

Recent Enhancements:

• Two-pass customer matching for performance
• LoadFields optimization for reduced data transfer
• Enhanced error handling and retry logic
• Improved JSON parsing for large documents

Upgrade Path

From Older Versions:

1. Backup environment
2. Test in sandbox first
3. Upload new .app file
4. Data upgrade codeunit runs automatically
5. Review new configuration options
6. Test key workflows
7. Deploy to production

Data Migration:

Codeunit 12073506 (BRCConnectDataupgrade) handles:

• Schema changes
• Default value updates
• Codeunit assignment updates
• New field population

Support and Resources

Documentation

• Primary Docs: docs.brightcom.online/brcconnect
• Context-Sensitive Help: F1 in BC opens relevant documentation
• Privacy Statement: brightcom.se/kontakt

Support Contacts

• Publisher: BrightCom Solutions AB
• Website: brightcom.com
• Contact: brightcom.se/kontakt

Technical Support

Before Contacting Support:

1. Review Troubleshooting guide
2. Check error messages in BRC Connect Error List
3. Verify configuration in BRC Connect Setup
4. Gather environment details (BC version, BRC version)

Support Request Information:

• BC environment type (sandbox/production)
• BRC Connect version (25.0.25051.1)
• Error message (exact text)
• Entry No. or Content ID with issue
• Steps to reproduce
• Expected vs. actual behavior

Community Resources

• BrightCom customer portal
• BC community forums (for BC-related questions)
• Partner network for implementation assistance

App Metadata

Dependencies

Base Dependencies:

• Microsoft Dynamics 365 Business Central (25.0.0.0)

No External App Dependencies

Visible To (Test Apps)

These apps can access BRC Connect internals:

Data Retention

Automatic Cleanup

Configure automatic deletion of old data:

BRC Connect Setup:

• Delete Content After: Date formula (e.g., “30D” for 30 days)

Applies To:

• BRC Connect Entries
• BRC Connect Content
• BRC Connect Values

Recommended Settings:

• Sandbox: 7-14 days
• Production: 30-90 days
• High Volume: 14-30 days

Manual Cleanup

Run manual cleanup when needed:

1. Open BRC Connect Content
2. Filter Created Date < cutoff date
3. Filter Status = OK (only delete successfully processed)
4. Delete records
5. Related Values auto-delete (cascade)

Warning: Don’t delete records with Status = Error (may need for troubleshooting)

Performance Metrics

Typical Throughput

Order Processing:

• Simple orders: 100-200/minute
• Complex orders (10+ lines): 50-100/minute
• Depends on: validation complexity, BC performance, external API speed

Inventory Sync:

• Items: 1000-2000/minute
• Depends on: number of locations, BOM complexity

API Calls:

• Inbound: 50-100 requests/minute
• Outbound: 100-200 requests/minute
• Rate limiting: Configurable via job queue frequency

Optimization Tips

1. Increase Max Count: Higher Process Entry Max Count = more per run
2. Parallel Processing: Multiple job queue entries for same codeunit
3. Product Range Filtering: Reduce unnecessary data sync
4. Batch Acknowledgment: Acknowledge in batches vs. individual
5. Off-Peak Processing: Schedule heavy jobs during low-usage hours

Next Steps

• Setup Guide - Configure BRC Connect
• User Guide - Daily operations
• Troubleshooting - Problem resolution
• Integrations - Integration architecture