Repair Orders

Repair Orders are the core documents in the Quick Repair extension that allow technicians and managers to create, track, and manage repair jobs in a standardized, traceable way. Each repair order follows Business Central document handling patterns and provides comprehensive customer, contact, item, and order-specific information.

Overview

With Repair Orders, you can:

Create standardized repair documents with auto-assigned numbers
Track customer and contact information for each repair job
Record detailed item information including serial and lot numbers
Categorize repairs using Order Types, Statuses, and Package Conditions
Document repair details with Internal Notes (staff-only) and External Comments (customer-facing)
Track repair solutions and outcomes for consistent documentation
Maintain audit trails with creation tracking
Integrate with Business Central's customer and contact management

Understanding Repair Order Structure

A Repair Order contains six main information groups:

Document Information

No.: Auto-generated from number series defined in Repair Management Setup
Created By: User who created the repair order
Created DateTime: When the repair order was created

Customer and Contact Information

Customer No.: Optional link to Business Central Customer table
Customer Details: Name, address, city, postal code, country/region automatically populated from customer record
Contact No.: Optional contact person filtered by selected customer
Contact Details: Name, phone number, and email automatically populated from contact record

Item Information

Item No.: Link to Business Central Item table
Item Description: Automatically populated from item record
Serial No.: Free-text field for item serial number
Lot No.: Free-text field for item lot number

Order Details

Order Type: Categorization using predefined repair order types
Order Status: Current status using predefined repair statuses with optional automatic default assignment
Package Condition: Condition of received item using predefined package conditions
Package Condition Comments: Free text field (up to 100 characters) for additional details about package condition
External Claim Number: Text field (up to 30 characters) for tracking insurance claims, warranty cases, or external system references
Cr. Note Required: Boolean field indicating if the order requires a credit note instead of repair

Retail Customer Information

Retail Customer Doc. No.: Reference to the customer's original receipt or sales document (up to 30 characters)
Retail Customer Sales Date: Date of the original retail sale transaction
Duplicate Detection: Intelligent duplicate detection for Retail Customer Doc. No. to prevent conflicts while maintaining workflow flexibility

Retail Customer Reference Tracking

The Retail Customer fields provide a direct link between repair orders and the original retail transaction. This is essential for warranty tracking, customer service efficiency, and ensuring accurate cross-referencing with sales records. The duplicate detection helps identify potential conflicts while remaining non-blocking to accommodate legitimate business scenarios.

Default Status Assignment

When creating new repair orders, if no status is manually specified and a default status is configured in the Repair Statuses setup, the system automatically assigns the default status. This ensures consistent workflow initiation while still allowing manual status selection when needed.

Resource Information

Resource No.: Link to Business Central Resource table, representing the person or machine performing the repair
Resource Quantity: Decimal field for the quantity of resource time used on the repair (e.g., number of hours)
Resource Time UoM Code: Unit of measure code for the resource time (e.g., HOUR, DAY). Filtered by the selected Resource No. — only units configured for that resource are available

Automatic Resource Defaults

When creating new repair orders, the Resource No., Resource Quantity, and Resource Time UoM Code are automatically pre-filled from the Repair Management Setup. When a Repair Technician is assigned and has a default resource configured, the resource changes to the technician's default, and the quantity and UoM reset to the setup defaults. Users can manually adjust these values on individual orders.

Fault Description

Fault Description: Comprehensive multiline field supporting up to 1,024 characters for documenting the reported issue
Multiline Support: Allows detailed fault descriptions with line breaks for better organization
Customer Communication: Essential for understanding the customer's reported problem and ensuring accurate diagnosis
Repair Documentation: Provides technicians with detailed information about the reported fault for effective troubleshooting

Internal Notes

Internal Notes: Free-text field supporting up to 1,024 characters for internal communication
Multiline Support: Allows detailed internal documentation and instructions
Internal Use Only: Notes are not included in customer-facing reports or external printouts

External Comments

External Comments: Customer-facing field supporting up to 1,024 characters for external communication
Multiline Support: Allows detailed customer-visible documentation and information
Customer-Facing: Comments may be included on external printouts, reports, or shared with customers
Professional Communication: Use for information that should be visible to customers such as repair explanations, warranty information, or delivery instructions

Repair Order Solutions

Solutions: Standardized solution codes documenting repair outcomes and resolutions
Multiple Solutions: Support for multiple solution entries per repair order
Solution Integration: Links to the Repair Solutions master data for consistent documentation
Outcome Tracking: Provides structured documentation of what was accomplished during the repair
Automatic Item Lines: When a solution is added, item lines (repair parts) linked to the solution via Item Repair Solutions are automatically created on the repair order. When a solution is removed, the related item lines are automatically cleaned up. See Repair Order Lines for details
Add Item Solutions: Bulk-add solutions from the item's predefined solution list using the Add Item Solutions action on the Solutions subpage

Credit Note Required Feature

The Credit Note Required feature allows repair orders to be flagged when a credit note should be issued instead of performing a standard repair. This feature ensures that finance-related follow-up processes are not missed and provides clear notifications to users about credit note requirements.

Overview

The Credit Note Required functionality provides:

Automatic Field Inheritance: When an item is selected, the Cr. Note Required field automatically inherits the setting from the item's repair configuration
Automatic Status Assignment: When Cr. Note Required is set to true, the system can automatically assign a predefined repair status
Manual Override Capability: Users can manually set or clear the Cr. Note Required field regardless of the item's default setting
Smart Notifications: Context-aware notifications that appear when credit notes are required or when status changes may need review
Integration: Full integration with API endpoints for external system access
Finance Workflow Support: Clear indication that alternative financial processing is needed

Field Behavior

Automatic Inheritance from Items

When the Item No. field is populated on a repair order:

Inheritance Logic: The system automatically checks the item's Cr. Note Required setting from the Item Repair Settings
Field Population: The repair order's Cr. Note Required field inherits the item's setting (true or false)
Notification Trigger: If inherited as true, a notification immediately appears to alert users
Description Update: The Item Description is populated simultaneously with the field inheritance

Manual Override Capability

Users can manually modify the Cr. Note Required field:

Override to True: Users can manually set the field to true even if the item doesn't require a credit note
Override to False: Users can clear the field even if the item's default setting requires a credit note
Immediate Notification: Manual changes trigger immediate notification updates
Independence: Manual settings are independent of the item's configuration

Field Clearing Behavior

When the Item No. field is cleared:

Automatic Reset: The Cr. Note Required field automatically resets to false
Notification Recall: Any displayed credit note notifications are automatically recalled
Clean State: The repair order returns to a clean state without credit note requirements

Automatic Status Assignment

When the Cr. Note Required field is set to true, the system can automatically assign a predefined repair status to ensure consistent workflow routing for credit note scenarios.

How Automatic Status Assignment Works

Configuration: A default status for credit note required scenarios is configured in the Repair Management Setup
Trigger Conditions: Automatic status assignment occurs when:
The Cr. Note Required field is manually set to true
An item with Cr. Note Required = true is selected on a repair order
The field value changes to true through any validation process
Status Assignment: If a default status is configured, the repair order's Order Status field is automatically updated
No Override: If the repair order already has a status assigned, automatic assignment respects existing values

Benefits of Automatic Status Assignment

Workflow Consistency: All credit note scenarios follow the same status progression
Reduced Manual Entry: Eliminates the need to manually set status on each credit note order
Clear Routing: Finance and repair teams immediately understand the order type through consistent status coding
Audit Trail: Status changes are tracked normally through Business Central's standard change logging

Configuration Requirements

For automatic status assignment to work:

Setup Configuration: The default status must be configured in Repair Management Setup
Status Existence: The configured default status must exist in the Repair Statuses master data
Permissions: Users must have permission to modify the Order Status field on repair orders

Status Selection Strategy

Choose a default status that clearly indicates financial processing is needed, such as "CREDIT NOTE", "FINANCE REVIEW", or "AWAITING REFUND". This status should route orders to appropriate finance personnel and distinguish them from standard repair workflows.

Credit Note Notifications

The system provides intelligent notification management for credit note requirements:

When Notifications Appear

Credit note notifications are displayed:

Credit Note Required Notifications: - Item Selection: When selecting an item that requires a credit note - Manual Setting: When manually setting the Cr. Note Required field to true - Page Opening: When opening a repair order page where Cr. Note Required is already true - Field Validation: When the field value changes to true through any validation process

Credit Note Disabled Notifications: - Field Change: When manually changing the Cr. Note Required field from true to false - Status Context: Only appears if a default status for credit notes is configured in setup - One-Time Display: Shown only at the moment of the status change, not on subsequent page openings

Notification Content

The system displays two types of credit note notifications:

Credit Note Required Notification When Cr. Note Required is set to true, the notification displays:

"The order requires a Credit Note. Please make sure to create proper finance documents."

This message provides: - Clear Requirement: Unambiguous indication that credit note processing is needed - Action Guidance: Reminds users to create appropriate financial documents - Professional Tone: Maintains business-appropriate communication style

Credit Note Disabled Notification When Cr. Note Required is changed from true to false (and a default status is configured), the notification displays:

"Cr. Note Required was disabled. Please verify and update the Repair Order Status if necessary."

This message provides: - Change Alert: Notifies users that credit note requirements have been removed - Status Review Reminder: Prompts users to verify that the repair order status is still appropriate - Workflow Guidance: Ensures manual review when credit note processing is no longer needed

Notification Control

The "Cr. Note Required was disabled" notification can be suppressed by enabling the "Skip Message on Cr. Status" setting in Repair Management Setup. This is useful for high-volume environments or experienced users who don't need these reminders.

When Notifications Disappear

Notifications are automatically recalled:

Field Cleared: When the Cr. Note Required field is set to false
Item Removal: When the Item No. field is cleared
Page Closure: When the repair order page is closed
Session Management: During page navigation to prevent notification accumulation

Notification Behavior

Single Display: Only one credit note notification appears at a time per repair order
Session Scope: Notifications are scoped to the current page session
Non-Persistent: Notifications don't persist across page reloads or navigation
Smart Recall: Previous notifications are automatically recalled before displaying new ones

External Claim Number Feature

The External Claim Number feature provides a dedicated field for tracking insurance claims, warranty claims, and other external reference numbers associated with repair orders. This feature helps maintain clear connections between repair work and external processes while providing intelligent duplicate detection to prevent conflicts.

Understanding External Claim Numbers

The External Claim Number field allows you to:

Track Insurance Claims: Link repair orders to insurance claim numbers for seamless processing
Reference Warranty Claims: Connect repairs to manufacturer warranty cases and reference numbers
External System Integration: Maintain references to external systems like third-party claim management platforms
Cross-Reference Documentation: Link repair work to external documentation and case numbers
Multi-Provider Support: Accommodate different numbering formats from various insurance and warranty providers

Duplicate Detection System

The External Claim Number field includes sophisticated duplicate detection that helps identify potential conflicts:

How Duplicate Detection Works

Real-Time Checking: When you enter or modify an External Claim Number, the system immediately searches for existing repair orders with the same claim number
Cross-Order Validation: The system checks all repair orders except the current one being edited
Case-Sensitive Matching: Claim numbers are matched exactly as entered, including case sensitivity
Immediate Feedback: If a duplicate is found, you receive a message with details about where the claim number is already used

Duplicate Warning Message

When a duplicate claim number is detected, you'll see this message:

Duplicate Claim Number Detected

"External Claim Number [CLAIM_NUMBER] already exists on Repair Order [ORDER_NUMBER]. Please verify the claim number is correct."

Non-Blocking Design Philosophy

The duplicate detection is designed to be informational rather than restrictive:

User Control: You remain in full control of whether to proceed or change the claim number
Flexibility: Accommodates legitimate scenarios where the same claim number might need to appear on multiple repair orders
Workflow Continuity: Doesn't interrupt repair order creation or editing workflows
Warning-Based: Provides information to help you make informed decisions

Retail Customer Information Feature

The Retail Customer Information feature provides dedicated fields for linking repair orders to original retail transactions. This feature ensures accurate cross-referencing with sales records, supports warranty tracking, and improves customer service efficiency by maintaining clear connections between repair work and the original purchase.

Understanding Retail Customer Fields

The Retail Customer Information feature provides two essential fields:

Retail Customer Doc. No. - Purpose: Links repair orders to customer's original receipt or sales document number - Format: Text field supporting up to 30 characters to accommodate various receipt numbering systems - Flexibility: Accepts any alphanumeric format to work with different POS systems and receipt formats - Customer Service: Helps staff quickly locate purchase history and warranty information

Retail Customer Sales Date - Purpose: Records the date of the original retail sale transaction - Format: Standard date field supporting all Business Central date formats - Warranty Tracking: Essential for calculating warranty periods and eligibility - Business Intelligence: Enables analysis of time between purchase and repair requests - Customer Communication: Provides context for warranty discussions and service planning

Retail Customer Duplicate Detection

The Retail Customer Doc. No. field includes intelligent duplicate detection designed to identify potential conflicts while maintaining workflow flexibility:

How Duplicate Detection Works

Real-Time Validation: When you enter or modify a Retail Customer Doc. No., the system immediately searches for existing repair orders with the same document number
Cross-Order Checking: The system examines all repair orders except the current one being edited
Exact Matching: Document numbers are matched precisely as entered, including case sensitivity and special characters
Immediate Feedback: If a duplicate is found, you receive a detailed warning message with information about the conflicting repair order

Duplicate Warning System

When a duplicate retail customer document number is detected, the system displays:

Duplicate Document Number Detected

"Retail Customer Doc. No. [DOCUMENT_NUMBER] already exists on Repair Order [ORDER_NUMBER]. Please verify the document number is correct."

This warning provides: - Specific Information: Shows exactly which document number is duplicated and where - Order Reference: Identifies the conflicting repair order number for easy lookup - Verification Prompt: Encourages you to double-check the document number accuracy

Non-Blocking Design Philosophy

The duplicate detection system is designed to be informational rather than restrictive:

User Control - You retain full control over whether to proceed with the duplicate number or change it - The warning doesn't prevent saving the repair order or continuing with the workflow - Final decision-making remains with the user based on business context

Business Flexibility - Accommodates legitimate scenarios where the same document number might appear on multiple repair orders - Supports situations like multiple items from one purchase requiring separate repairs - Allows correction of previously entered incorrect document numbers

Workflow Efficiency - Doesn't interrupt repair order creation or editing processes - Provides helpful information without blocking standard operations - Maintains smooth workflow while adding valuable data validation

Creating a New Repair Order

Prerequisites

The Quick Repair extension must be installed and configured
Repair Management Setup must be completed with number series configuration
You must have Technician or Manager permissions

Step-by-Step Creation

Access Repair Orders
In Business Central, use the search function (Alt+Q) to find and open Repair Orders
On the Repair Orders page, select New to create a new repair order
Document Number Assignment
The No. field will automatically populate with the next number from the configured number series
To manually enter a number, use the AssistEdit button (three dots) next to the No. field
The system validates manual numbers against the number series configuration
Enter Customer Information (Optional)
Customer No.: Select from existing customers using the lookup
When a customer is selected, the following fields populate automatically:
- Customer Name
- Address and Address 2
- City, Post Code, County
- Country/Region Code
Enter Contact Information (Optional)
Contact No.: Select from contacts related to the chosen customer
When a contact is selected, the following fields populate automatically:
- Contact Name
- Phone No.
- Email

!!! note "Contact Filtering" If a customer is selected, the contact lookup automatically filters to show only contacts related to that customer through business relationships.

Enter Item Information
Item No.: Select the item being repaired from the Item table
Item Description: Automatically populated from the item record
Serial No.: Enter the serial number of the specific item (free text)
Lot No.: Enter the lot number if applicable (free text)

!!! warning "Repair Restrictions" Some items may have repair restrictions configured that prevent repair order creation. If you encounter an error when selecting an item, check the item's Repair Settings to verify if "Repair Not Allowed" is enabled. Items with this restriction cannot be used in repair orders until the restriction is removed by a manager.

!!! note "Credit Note Inheritance" When selecting an item, the Cr. Note Required field automatically inherits the setting from the item's repair configuration. If the item requires a credit note, you'll see an immediate notification reminding you to create proper finance documents. You can manually override this setting if needed.

Set Order Details
Order Type: Select from configured Repair Order Types
Order Status: Select from configured Repair Statuses

!!! note "Automatic Default Status" If no status is specified and a default status is configured in Repair Statuses setup, the system will automatically assign the default status to the new repair order. Learn more about Default Status Configuration.
Package Condition: Select from configured Package Conditions
Package Condition Comments: Enter additional details about the package condition upon receipt
- Character Limit: Up to 100 characters for supplementary condition notes
- Free Text: Allows detailed observations beyond the standard condition classification
- Example Usage: "Missing power cord", "Slight water damage on base", "Box opened upon arrival"
External Claim Number: Enter the external claim number for insurance or warranty purposes
- Character Limit: Up to 30 characters for claim number tracking
- Format Flexibility: Accepts any alphanumeric format to accommodate different insurance and warranty providers
- Duplicate Detection: System alerts if the same claim number is already used on another repair order
- Non-Blocking Warning: Duplicate warnings are informational only - you can still save the repair order
- Insurance Integration: Facilitates tracking and cross-referencing with external insurance and warranty systems
Cr. Note Required: This field automatically inherits from the selected item's configuration but can be manually overridden
- Automatic Setting: When an item requires a credit note, this field is automatically set to true
- Manual Override: You can manually set or clear this field as needed
- Notification: If set to true, you'll see a notification reminding you to create proper finance documents
Enter Retail Customer Information (Optional)
Retail Customer Doc. No.: Enter the customer's original receipt or sales document number
- Character Limit: Up to 30 characters for document number reference
- Format Flexibility: Accepts any alphanumeric format to accommodate different POS and receipt systems
- Cross-Reference: Helps link repair orders to original retail transactions for warranty and customer service
- Duplicate Detection: System alerts if the same document number is already used on another repair order
- Non-Blocking Warning: Duplicate warnings are informational only - you can still save the repair order if needed
- Example Usage: Receipt numbers, invoice numbers, or POS transaction IDs
Retail Customer Sales Date: Enter the date of the original retail sale
- Warranty Tracking: Essential for calculating warranty periods and eligibility
- Business Intelligence: Enables analysis of time between purchase and repair requests
- Customer Service: Provides context for warranty discussions and service planning
- Format: Standard Business Central date field supporting all regional date formats

!!! tip "Retail Customer Information Best Practices" Always enter both the document number and sales date when available. This information is crucial for warranty tracking, customer service efficiency, and maintaining accurate cross-references with sales records. The duplicate detection helps identify potential conflicts but won't prevent legitimate business scenarios where the same receipt might cover multiple items requiring separate repairs.

Document Fault Description
Fault Description: Enter a detailed description of the reported issue or problem with the item
Multiline Input: Use Enter key to create line breaks for better organization and readability
Character Limit: Up to 1,024 characters available for comprehensive fault documentation
Customer Information: Record exactly what the customer reported as the problem or symptoms
Diagnostic Aid: Provide technicians with detailed information to understand the issue before beginning repair work

!!! tip "Fault Description Best Practices" Include specific symptoms, error messages, when the problem occurs, and any relevant customer observations. This information is crucial for accurate diagnosis and efficient repair planning. Be as detailed as possible - more information helps technicians work more effectively.

Add Internal Notes (Optional)
Internal Notes: Enter detailed internal communication, technical instructions, or special handling notes
Multiline Input: Use Enter key to create line breaks for organized information
Character Limit: Up to 1,024 characters available for comprehensive documentation
Internal Use Only: These notes are for staff reference and will not appear on customer documents

!!! note "Internal Notes Usage" Internal Notes are designed for communication between technicians, managers, and support staff. Use this field to document special customer requirements, technical observations, parts availability issues, or any other information that helps the repair team but should remain confidential.

Add External Comments (Optional)
External Comments: Enter customer-facing information that may be shared externally
Multiline Input: Use Enter key to create line breaks for organized presentation
Character Limit: Up to 1,024 characters available for comprehensive customer communication
Customer-Visible: These comments may appear on customer documents, reports, or printouts

!!! note "External Comments Usage" External Comments are designed for professional communication with customers. Use this field for repair explanations, warranty information, delivery instructions, or any information that should be visible to customers. Ensure content is professional and appropriate for external viewing.

Save the Repair Order
The repair order is automatically saved when you navigate away or close the page
Creation details (Created By and Created DateTime) are automatically recorded

Adding Predefined External Comments

The Quick Repair extension provides powerful actions to quickly add predefined external comments to repair orders. These actions help ensure consistent, professional customer communication while saving time during repair documentation.

External Comment Actions

On the Repair Order Card, use the ribbon actions to add predefined comments:

Add External Comments

Purpose: Select from all available predefined external comments
Usage: Opens a selection dialog showing all external comment definitions
Selection: Use checkboxes to select multiple comments for addition
Ordering: Comments are added in order priority, then by code
Benefit: Provides access to the complete library of predefined comments

How to Use: 1. Click Add External Comments in the ribbon 2. Review the available predefined comments in the selection dialog 3. Use the checkboxes to select desired comments 4. Click OK to append selected comments to the External Comments field

Type-Specific Comment Actions

For faster access to categorized comments, use specialized actions:

Add Accepted Comment - Purpose: Quickly adds all "Complaint Accepted" type comments - Use Case: When honoring warranty claims or providing goodwill repairs - Efficiency: Automatically includes all relevant acceptance comments - Professional: Ensures consistent acknowledgment of customer concerns

Add Rejected Comment
- Purpose: Adds all "Complaint Rejected" type comments - Use Case: When declining warranty coverage or complaint requests - Clarity: Provides professional explanations for rejection decisions - Policy Compliance: Ensures rejections follow company guidelines

Add No-repair Statement - Purpose: Adds all "No-repair Statement" type comments
- Use Case: When repair is not feasible, economical, or recommended - Alternatives: Explains options like replacement or upgrade recommendations - Transparency: Clearly communicates why repair cannot proceed

Comment Addition Behavior

Appending Content - Comments are always appended to existing External Comments content - Existing content is not overwritten when adding the general comments - Existing content is overwritten only if the action adds type-specific comments (e.g., Accepted, Rejected, No-repair) - New comments are separated from existing content with spaces - Multiple comments are combined with appropriate spacing

Character Limit Management - External Comments field supports up to 1,024 characters total - System automatically validates total length when adding comments - Warning displayed if character limit would be exceeded - Only fitting content is added if limit is reached

Automatic Ordering - Predefined comments are added based on their Order field - Comments with lower order numbers appear first - Comments with the same order are sorted alphabetically by Code - This ensures consistent, logical flow of information

Setting Up Predefined Comments

To configure the predefined comments used by these actions:

Access Configuration: Navigate to Repair External Comment Definitions under Administration
Create Definitions: Set up predefined comments with appropriate types
Set Categories: Assign Comment Types (Complaint Accepted, Complaint Rejected, No-repair Statement)
Order Priority: Use Order field to control sequence of comments
Test Actions: Verify actions work correctly with your comment definitions

For detailed setup instructions, see External Comment Definitions.

Best Practices for Comment Actions

Strategic Usage - Use type-specific actions for common scenarios (warranty decisions, repair outcomes) - Use general Add External Comments for custom comment combinations - Combine multiple actions when repair situations require varied communication - Review total content length when using multiple comment additions

Quality Assurance - Regularly review predefined comment content for accuracy and professionalism - Ensure comment types are assigned correctly for effective filtering - Train staff on appropriate action selection for different repair scenarios - Monitor customer feedback to improve comment effectiveness

Workflow Integration - Integrate comment actions into standard repair workflows - Use actions at appropriate stages of repair process (acceptance, completion, rejection) - Combine with status updates for comprehensive customer communication - Document usage patterns to optimize comment library organization

Adding Solutions and Automatic Item Lines

Solution-Driven Repair Parts

When solutions are added to a Repair Order, the system can automatically create repair order lines (parts) based on the items linked to each solution. This automation reduces manual data entry, ensures consistency, and helps technicians quickly assemble the correct parts list for each repair.

The automatic behavior relies on Item Repair Solutions — the predefined relationships between items and repair solutions. Each item-solution relationship can optionally be marked as Unique on Order to prevent duplicate lines.

Adding Solutions Manually

You can add solutions directly on the Repair Order Solutions subpage by selecting a Solution Code from the lookup. When a solution is validated:

The system checks for items linked to the solution in the Item Repair Solution table
For each linked item, a Repair Order Line is created with Quantity = 1
Items marked as "Unique on Order" are not duplicated if they already exist on the order

Add Item Solutions Action

The Add Item Solutions action on the Repair Order Solutions subpage allows you to bulk-add multiple solutions at once from the repair order item's predefined solution list.

How to Use:

Open the Repair Order Card for the order you want to add solutions to
Ensure an Item No. is set on the repair order header
On the Repair Order Solutions subpage, click the Add Item Solutions action
A dialog opens showing all repair solutions configured for the order's item
Select multiple solutions by holding Ctrl and clicking the desired rows
Click OK to add the selected solutions

Multi-Select

Hold Ctrl while clicking to select multiple solutions in the dialog. All selected solutions are added to the repair order at once, and item lines are automatically created for each.

Requirements:

An item must be assigned to the repair order. If no item is set, the system displays an error message
Solutions that already exist on the order are skipped (no duplicates created)

Automatic Line Removal on Solution Delete

When a solution is deleted from the Repair Order Solutions subpage, the system automatically handles the related repair order lines:

Unconsumed lines (Qty. Consumed = 0) are removed
Consumed lines (Qty. Consumed > 0) are preserved to protect consumption records
Unique on Order items referenced by other remaining solutions are reassigned rather than deleted

For full details on automatic line management, see Repair Order Lines — Automatic Line Management.

Managing Repair Orders

Viewing Repair Orders

The Repair Orders list page provides an overview of all repair orders with key information:

Document number
Customer name and number
Contact name
Item number and description
Serial number
Order type and status
Cr. Note Required - Boolean indicator for credit note requirements
Package condition
External Claim Number - External claim reference for insurance/warranty tracking
Retail Customer Doc. No. - Customer receipt/invoice number (optionally visible - use personalization to show/hide)
Retail Customer Sales Date - Original sales date (optionally visible - use personalization to show/hide)
Package Condition Comments (optionally visible - use personalization to show/hide)
Fault Description (optionally visible - use personalization to show/hide)
Internal Notes (optionally visible - use personalization to show/hide)
External Comments (optionally visible - use personalization to show/hide)

Editing Repair Orders

Open the Repair Orders list page
Select the repair order you want to edit
Double-click or use the Edit action to open the repair order card
Make your changes and close the page to save

Search and Filtering

Use Business Central's standard filtering and search capabilities:

Quick Filter: Use the search box at the top of the list to find specific repair orders
Column Filters: Click on column headers to set specific filters
Advanced Filters: Use the filter pane for complex filtering scenarios

Customer and Contact Validation

The repair order system includes built-in validation:

Customer Validation: When a Customer No. is entered, the system validates it exists and populates related fields
Contact Validation: When a Contact No. is entered, the system ensures the contact is related to the selected customer
Email Validation: Email addresses are validated using Business Central's standard email validation

Field Behavior and Dependencies

Understanding how fields interact helps ensure data accuracy:

Customer Field Dependencies

Clearing the Customer No. automatically clears all customer-related fields and contact fields
Changing the Customer No. clears contact fields but updates customer-related fields with new customer data
Customer name can be used for lookup when search by name is enabled in setup

Contact Field Dependencies

Clearing the Contact No. clears all contact-related fields
Contact selection is filtered by the selected customer's business relationships
Clearing the Contact Name automatically clears the Contact No.

Item Field Dependencies

Clearing the Item No. automatically clears the Item Description and Cr. Note Required field
Setting an Item No. automatically populates the Item Description from the item record
Setting an Item No. automatically inherits the Cr. Note Required setting from the item's repair configuration

Automatic Lifecycle Date Tracking

Quick Repair automatically tracks key milestone dates throughout the repair process using intelligent date population based on status changes. This feature provides accurate timeline tracking and helps monitor repair workflow performance.

Understanding Lifecycle Dates

The system tracks four critical dates in the repair lifecycle:

Field	Description	Populated When
Receive Date	When the equipment was received and logged	Status changes to "Received"
Start Date	When repair work actually began	Status changes to "In Progress"
Finished Date	When all repair work was completed	Status changes to "Repair Finished"
Shipment Date	When equipment was returned to customer	Status changes to "Shipped"

Important: Different Date Behaviors

Start Date has special behavior compared to other lifecycle dates:

Start Date: Set once when first entering "In Progress" status, then preserved permanently
Other Dates: Allow updates with user confirmation to accommodate workflow changes

This design ensures the true start of repair work is accurately tracked, even if the repair process involves multiple status changes.

How Automatic Population Works

Lifecycle dates are automatically populated when the repair order status is changed to match specific standard status values:

User Changes Status: When a user updates the Order Status field to a status with a corresponding standard status mapping
System Detection: The system detects the standard status mapping (Received, In Progress, Repair Finished, or Shipped)
Date Population: The system populates the corresponding lifecycle date field based on the specific field's behavior
Different Behaviors: Each lifecycle date field has its own population rules for data integrity

Date Population Behavior by Field

The system uses different approaches for each lifecycle date to ensure data accuracy:

Start Date (In Progress Status) - Set-Once Behavior: Automatically populated only if the field is empty - No Overwrite: Once set, the date is preserved even if status changes back to In Progress - No Confirmation: No user prompt since existing dates are never overwritten - Business Logic: Ensures the first time repair work begins is accurately recorded

Other Lifecycle Dates (Receive, Finished, Shipment) - Confirmation Required: System asks for confirmation before overwriting existing dates - User Choice: Users can choose to update the date or keep the current value - Flexible Updates: Allows correcting dates when workflow changes occur - Data Protection: Prevents accidental loss of important milestone dates

User Confirmation Process

For dates that support overwriting (Receive Date, Finished Date, Shipment Date):

Empty Date Fields: Automatically populated without prompts
Existing Date Fields: System displays a confirmation dialog: "[Field Name] is already set. Do you want to overwrite it?"
User Response:
Yes: Current date replaces the existing date
No: Existing date is preserved, status change still processed

Example Workflow Timeline

Here's how lifecycle dates track a typical repair process:

Day 1: Equipment received → Status changed to "LOGGED" (mapped to Received) → Receive Date set to Day 1
Day 3: Diagnosis complete, repair begins → Status changed to "REPAIRING" (mapped to In Progress) → Start Date set to Day 3
Day 5: Issue found, waiting for parts → Status changed to "WAITING" → No date changes (Start Date preserved)
Day 6: Parts arrived, resume work → Status changed back to "REPAIRING" → Start Date unchanged (still Day 3)
Day 7: Repair completed → Status changed to "READY" (mapped to Repair Finished) → Finished Date set to Day 7
Day 9: Customer collected equipment → Status changed to "COLLECTED" (mapped to Shipped) → Shipment Date set to Day 9

Key Points: - Start Date Preservation: When returning to "In Progress" status (Day 6), the original Start Date (Day 3) is maintained - Accurate Timeline: The repair truly started on Day 3, not when work resumed on Day 6 - Confirmation Protection: If Day 7 status change was accidental, user could decline to overwrite Finished Date

Benefits of Lifecycle Date Tracking

Performance Monitoring - Track average repair times from receipt to completion - Identify bottlenecks in the repair workflow - Monitor technician and department performance - Generate accurate delivery time estimates

Customer Communication - Provide accurate status updates with specific dates - Set realistic expectations for completion times - Demonstrate service efficiency and reliability - Support warranty and service level agreement tracking

Business Intelligence - Analyze repair workflow efficiency - Identify seasonal patterns and capacity needs - Support resource planning and scheduling - Generate comprehensive repair analytics

Customizing Lifecycle Date Behavior

The lifecycle date system integrates with your custom status configuration:

Standard Status Mapping: Custom statuses must map to standard status values to trigger date population
Flexible Workflow: Multiple custom statuses can map to the same standard status
Non-Linear Process: Repairs can move between statuses without following a strict sequence
Manual Override: Users can manually adjust dates when automatic population doesn't reflect actual workflow

Best Practices for Lifecycle Dates

Status Management - Ensure custom statuses are properly mapped to standard status values - Train staff on the importance of timely status updates for accurate date recording - Use status changes to accurately reflect actual workflow milestones - Understand that Start Date behavior differs from other lifecycle dates

Data Quality and Date Behavior - Start Date: Record the true beginning of repair work - this date is preserved throughout the repair process - Other Dates: Use confirmation prompts thoughtfully to maintain data accuracy when workflow changes occur - Verify dates reflect actual events, not just convenient system updates - Correct dates manually when system automation doesn't match reality

Workflow Optimization - Use lifecycle date reports to identify process improvements - Monitor Start Date consistency to ensure repair commencement is accurately tracked - Track milestone timing to improve customer communication - Analyze date patterns to optimize resource allocation and support continuous improvement

Troubleshooting Lifecycle Dates

Common Scenarios and Solutions

"Start Date didn't update when I changed status to In Progress" - Cause: Start Date was already set from a previous status change - Solution: This is expected behavior - Start Date preserves the original repair commencement time - Manual Fix: If you need to change Start Date, edit the field directly in the repair order

"System prompted to overwrite a date I didn't want to change" - Cause: Status change triggers date population for dates that already have values - Solution: Click "No" in the confirmation dialog to preserve the existing date - Prevention: Review status mappings to ensure they align with your intended workflow

"Wrong date was set automatically" - Cause: Status change occurred on a different day than the actual milestone - Solution: Manually edit the lifecycle date field to reflect the correct date - Prevention: Update status promptly when milestones actually occur

"Lifecycle dates not populating at all" - Cause: Custom statuses may not be mapped to standard status values - Solution: Check your repair status setup to ensure proper standard status mapping - Verification: Confirm that your status has the correct Standard Status field value

Manual Date Corrections

When automatic population doesn't match reality:

Direct Field Editing: Lifecycle date fields can be manually updated if needed
Business Justification: Document reasons for manual changes in notes or comments
Audit Considerations: Manual changes should reflect actual business events
System Integration: Manual dates work seamlessly with reporting and analytics

Document Attachments

The Repair Order Card includes a Document Attachment factbox that allows you to store and access files directly from the repair order. This uses standard Business Central document attachment functionality — no custom setup is required.

What You Can Do

Upload files: Click the attachment icon or use the upload action in the factbox to add files
Drag and drop: Drag files directly onto the factbox to attach them
View attachments: Click on an attachment to open or download it
Delete attachments: Remove attachments that are no longer needed
View details: See file name, file type, and upload date for each attachment

Common Use Cases

Photos: Before/after repair photos, damage documentation
Receipts: Purchase receipts, warranty cards, proof of purchase
Diagnostics: Diagnostic reports, test results, error logs
Correspondence: Customer emails, insurance documents, claim forms

How Attachments Work

Attachments are linked to the specific Repair Order using the document number
Each repair order maintains its own set of attachments, independent of other orders
The factbox appears in the right panel of the Repair Order Card, above Notes and Links
Attachments follow standard Business Central permissions — no additional permission setup is needed

Attachment Best Practices

Attach relevant documentation at the time of receipt (photos of condition, customer receipts) to establish a clear record. Use descriptive file names so attachments can be easily identified without opening them.

Item Picture Factbox

The Repair Order Card includes a read-only Item Picture factbox that displays the picture of the item assigned to the repair order. This allows technicians and managers to quickly identify the item being repaired without navigating to the Item Card.

How It Works

The factbox displays the picture of the item specified in the Item No. field on the repair order header
When the Item No. changes, the picture updates automatically
If no item is assigned or the item has no picture, the factbox shows an empty state
The factbox is read-only — pictures cannot be uploaded, modified, or deleted from the repair order. To manage item pictures, use the Item Card

Where to Find It

The Item Picture factbox appears in the right panel of the Repair Order Card, at the top of the factbox area (above Document Attachments, Notes, and Links).

Adding Pictures to Items

Item pictures are managed on the Item Card in Business Central. Navigate to the item and use the Picture action to upload or change the image. Once set, the picture will automatically appear on all repair orders referencing that item.

Best Practices

Data Entry Efficiency

Use Lookups: Take advantage of customer and item lookups rather than typing codes manually
Customer-First Workflow: Enter customer information before contact details to benefit from contact filtering
Consistent Naming: Use consistent serial and lot number formats for better tracking

Data Quality

Verify Customer Information: Ensure customer data is current before creating repair orders
Contact Relationships: Maintain proper business relationships between customers and contacts
Item Information: Keep item descriptions up-to-date for accurate repair documentation
Detailed Fault Descriptions: Record comprehensive fault information to aid diagnosis and repair planning

Fault Description Best Practices

Specific Symptoms: Document exact symptoms, error messages, and observable behaviors
Context Information: Include when the problem occurs (startup, during use, intermittently)
Customer Language: Use clear, descriptive language that both customers and technicians can understand
Environmental Factors: Note relevant conditions (temperature, humidity, usage patterns)

External Comments Best Practices

Professional Language: Use clear, professional language appropriate for customer communication
Repair Explanations: Document what was repaired, replaced, or adjusted in customer-friendly terms
Warranty Information: Include relevant warranty details, coverage periods, or exclusions
Care Instructions: Provide maintenance tips or usage recommendations to prevent future issues
Delivery Information: Add pickup instructions, delivery schedules, or special handling requirements
Avoid Technical Jargon: Use terminology that customers can easily understand
Previous Attempts: Record any customer attempts to resolve the issue
Impact Assessment: Describe how the fault affects the item's functionality

Package Condition Comments Best Practices

Supplement Standard Classifications: Use comments to provide specific details that standard condition codes cannot capture
Document Specific Issues: Record particular damage, missing components, or unusual conditions
Be Concise: With a 100-character limit, focus on the most important additional details
Use Clear Language: Write in simple, descriptive terms that anyone can understand
Examples of Good Comments:
"Missing power adapter and manual"
"Water damage visible on bottom panel"
"Significant scratches on display"
"Original packaging opened on arrival"
"Serial number label partially torn"
Accountability: Helps document the exact state upon receipt for warranty and liability purposes
Repair Planning: Provides technicians with specific condition details for repair assessment

Process Standardization

Order Types: Use appropriate order types for consistent categorization
Status Updates: Regularly update order status to reflect repair progress
Package Conditions: Document package condition accurately for accountability

Permissions

Different user roles have varying access levels to Repair Orders:

Role	Permissions	Description
Manager	Read, Insert, Modify, Delete	Full access to create, edit, and delete repair orders
Technician	Read, Insert, Modify, Delete	Full access to create, edit, and delete repair orders
Read Only	Read	Can only view existing repair orders

Permission Assignment

Permission sets are assigned through Business Central's standard user setup. Contact your system administrator to modify user permissions.

API Integration

Repair Orders are accessible through API pages for integration with external systems:

Repair Order API: Provides programmatic access to repair order data including fault descriptions and external comments
OData Support: Enables integration with external applications
Standard Business Central API Patterns: Follows Microsoft's API design guidelines
Fault Description Field: Available as faultDescription in API responses and requests
External Comments Field: Available as externalComments in API responses and requests for customer-facing integrations
External Claim Number Field: Available as externalClaimNumber in API responses and requests for insurance/warranty integration
Credit Note Required Field: Available as crNoteRequired in API responses and requests with automatic inheritance support
Resource Quantity Field: Available as resourceQuantity in API responses and requests for tracking labor time
Resource Time UoM Code Field: Available as resourceTimeUoMCode in API responses and requests for time unit of measure

Credit Note Required API Behavior

The Credit Note Required field provides sophisticated API integration capabilities:

Automatic Inheritance: When creating repair orders via API with an item number, the crNoteRequired field automatically inherits from the item's configuration
Manual Override: API calls can explicitly set the crNoteRequired field value to override item defaults
Read Access: External systems can query the credit note requirement status for finance integration
Write Access: External systems can modify credit note requirements as needed
Validation Rules: API calls respect the same inheritance and validation logic as manual entry
Field Clearing: When itemNo is cleared through API, crNoteRequired automatically resets to false

API Field Name: crNoteRequired (Boolean)
Default Behavior: Inherits from item configuration when item number is provided
Override Support: Accepts explicit true/false values to override inheritance

Troubleshooting

Common Issues

Q: I can't create new repair orders
A: Ensure you have the proper permissions (Technician or Manager) and that the Repair Management Setup includes a valid number series configuration.

Q: I get an error when selecting an item for repair
A: Check if the item has repair restrictions enabled. Navigate to the Item Card and check the Repair tab for "Repair Not Allowed" or "Cr. Note Required" settings. See Item Repair Settings for more information about managing these restrictions.

Q: Customer information isn't populating automatically
A: Verify that the customer number exists and that you're using the validation (pressing Tab or Enter) after entering the customer number.

Q: Contact lookup is showing all contacts instead of filtering by customer
A: Check that business relationships are properly configured between the customer and contacts in Business Central's contact management.

Q: I'm getting email validation errors
A: The system uses Business Central's standard email validation. Ensure email addresses follow proper format (e.g., user@domain.com).

Q: Manual number entry isn't working
A: Check that the number series in Repair Management Setup allows manual numbers and that your number falls within the defined range.

Q: Item description isn't populating
A: Verify that the item number exists in the Item table and that the item has a description defined.

Q: New repair orders aren't getting the expected default status
A: Check the Repair Statuses configuration to ensure a status is marked as default. Default status only applies when no status is manually specified during repair order creation.

Credit Note Required Issues

Q: The Cr. Note Required field isn't inheriting from the item
A: Verify that the item has the "Cr. Note Required" setting enabled in the Item Card's Repair tab. The field only inherits when an item is selected that has this setting configured. See Item Repair Settings for configuration details.

Q: I'm not seeing the credit note notification
A: Credit note notifications only appear when the "Cr. Note Required" field is set to true. Check that: - The field is actually set to true on the repair order - You haven't accidentally dismissed the notification - Notifications are enabled in your Business Central user settings

Q: The credit note notification keeps appearing repeatedly
A: This shouldn't happen as the system is designed to show the notification only once per session. If this occurs: - Try closing and reopening the repair order page - Clear the "Cr. Note Required" field and set it again - Contact your system administrator if the issue persists

Q: I can't override the Cr. Note Required field
A: The field should always be editable. If you cannot modify it: - Check that you have sufficient permissions for repair order editing - Verify you're on the correct field (not a display-only field) - Ensure the repair order is not in a read-only state

Q: The notification appears in the wrong language
A: The notification text uses your user's language setting. If the text appears in the wrong language: - Verify your user language settings in Business Central - Check that the Quick Repair extension includes translations for your language - Contact your administrator about language configuration

Q: Credit note notifications don't appear in the list view
A: Credit note notifications are only displayed on the repair order card page, not in list views. This is by design to avoid notification clutter. The "Cr. Note Required" column in list views provides visual indication without notifications.

Q: The default status assignment seems inconsistent
A: Verify that only one status is marked as default in the Repair Statuses setup. If multiple statuses appear to be default, unmarking and re-marking the intended default status should resolve the issue.

Lifecycle Date Issues

Q: Lifecycle dates aren't automatically populating when I change status
A: Check that your custom status is properly mapped to a standard status value in Repair Statuses. Only statuses mapped to Received, In Progress, Repair Finished, or Shipped trigger automatic date population.

Q: The system keeps asking for confirmation even when the date field is empty
A: This may indicate a hidden character or formatting issue in the date field. Clear the field completely and try changing the status again.

Q: I accidentally overwrote the wrong lifecycle date
A: Lifecycle dates can be manually corrected. Simply edit the date field directly to the correct value. The system only auto-populates based on status changes.

Q: Start Date didn't update when I changed back to In Progress status
A: This is expected behavior. Start Date has special set-once behavior - it preserves the original repair commencement date and never gets overwritten by subsequent status changes to In Progress. If you need to change the Start Date, edit it manually.

Q: Why doesn't Start Date ask for confirmation like other lifecycle dates?
A: Start Date uses different logic - it only gets set when empty, ensuring the true beginning of repair work is preserved. Other lifecycle dates (Receive, Finished, Shipment) allow updates with confirmation to accommodate workflow changes.

Q: Multiple status changes are updating the same lifecycle date repeatedly
A: This is expected behavior when multiple custom statuses map to the same standard status. If you need different timing, consider adjusting your status mappings or use manual date entry for specific cases. Note: Start Date is exempt from this behavior as it preserves the original value.

Q: The lifecycle dates don't match our actual workflow timing
A: The system populates dates when status changes occur, not when work actually happens. Train staff to update status only when milestones are actually reached, or manually adjust dates to reflect actual timing.

Fault Description Issues

Q: I can't see the Fault Description column in the list view
A: The Fault Description column is hidden by default. Use the Personalize feature to make it visible. Right-click on the column headers and select Personalize, then check the box for Fault Description.

Q: My Fault Description text is being cut off in the display
A: Fault Description supports up to 1,024 characters. In list view, only a preview is shown. Click on the repair order to view the full description in the card view's dedicated Fault Description tab, or hover over the field for an extended preview.

Q: I accidentally deleted part of my fault description
A: Use Ctrl+Z to undo recent changes, or navigate away from the field without saving to revert changes. For committed changes, re-enter the missing information. Consider copying long descriptions to a temporary location before major edits.

Q: Can I copy fault descriptions between repair orders?
A: Yes, you can copy and paste text from the fault description field like any text field. This is useful for similar issues or when creating templates for common problems.

Internal Notes Issues

Q: I can't see the Internal Notes column in the list view
A: The Internal Notes column is hidden by default. Use the Personalize feature to make it visible. Right-click on the column headers and select Personalize, then check the box for Internal Notes.

Q: My Internal Notes are being cut off in the display
A: Internal Notes support up to 1,024 characters. In list view, only a preview is shown. Click on the repair order to view the full notes in the card view, or hover over the field for an extended preview.

Q: Internal Notes appear on customer documents
A: This should not happen as Internal Notes are specifically excluded from customer-facing reports. If this occurs, verify you're using the correct report templates and contact support for assistance.

External Comments Issues

Q: I can't see the External Comments column in the list view
A: The External Comments column is hidden by default. Use the Personalize feature to make it visible. Right-click on the column headers and select Personalize, then check the box for External Comments.

Q: My External Comments are being cut off in the display
A: External Comments support up to 1,024 characters. In list view, only a preview is shown. Click on the repair order to view the full comments in the card view, or hover over the field for an extended preview.

Q: Will External Comments appear on customer documents?
A: External Comments are designed to be customer-facing and may be included on external printouts, reports, or shared with customers. Ensure content is professional and appropriate for external viewing.

Q: How do I distinguish between Internal Notes and External Comments?
A: On the repair order card, Internal Notes are labeled "Internal Notes (For Staff Only)" while External Comments are labeled "External Comments (Customer-Facing)" to clearly distinguish their purpose and audience.

Package Condition Comments Issues

Q: I can't see the Package Condition Comments field on the repair order card
A: The Package Condition Comments field is located in the Order Information section, directly below the Package Condition field. Ensure you have the latest version of the Quick Repair extension installed.

Q: My Package Condition Comments are being cut off
A: The Package Condition Comments field has a 100-character limit. Keep your comments concise and focus on the most important additional details. If you need more space, consider using the Internal Notes or External Comments fields for extended documentation.

Q: Should Package Condition Comments be visible to customers?
A: Package Condition Comments are primarily for internal documentation and accountability. While they may appear on internal reports, they are not typically included in customer-facing documents. Use External Comments for information intended for customer viewing.

Q: Can I use Package Condition Comments for tracking changes during repair?
A: Package Condition Comments are specifically for documenting the condition upon receipt. Use Internal Notes or External Comments to document condition changes that occur during the repair process.

External Claim Number Issues

Q: I keep getting duplicate claim number warnings but I know the number is correct
A: Duplicate warnings are informational and don't prevent saving. This may indicate legitimate scenarios where the same claim covers multiple repairs (e.g., multiple items from one insurance claim). You can proceed safely and document the relationship in Internal Notes if needed.

Q: The duplicate warning shows a repair order I can't find
A: The referenced repair order might be in a different status, assigned to another user, or you may not have access to view it. Use the repair order number from the warning message to search directly, or contact your administrator for assistance.

Q: My External Claim Number was truncated when I entered it
A: External Claim Numbers are limited to 30 characters. If your claim number is longer, use an abbreviated version or record the full number in Internal Notes for reference.

Q: I don't see the External Claim Number field on my repair order
A: The External Claim Number field is located in the Order Information section of the repair order card. Ensure you have the latest version of the Quick Repair extension installed and check that the field hasn't been hidden through personalization.

Q: The duplicate check isn't working - I can enter the same claim number multiple times
A: The duplicate detection provides warnings but doesn't block saving. This is intentional design to accommodate legitimate business scenarios. If you're not seeing any warnings when duplicates exist, contact your system administrator.

Q: Can I search for repair orders by External Claim Number?
A: Yes, you can use Business Central's standard filtering capabilities on the External Claim Number field in the Repair Orders list to find orders with specific claim numbers.

Retail Customer Information Issues

Q: I keep getting duplicate retail customer document number warnings but I know the number is correct
A: Duplicate warnings are informational and don't prevent saving. This is designed to accommodate legitimate scenarios where the same receipt might cover multiple items requiring separate repairs. You can proceed safely and document the relationship in Internal Notes if needed.

Q: The duplicate warning shows a repair order I can't find
A: The referenced repair order might be in a different status, assigned to another user, or you may not have access to view it. Use the repair order number from the warning message to search directly, or contact your administrator for assistance.

Q: I don't see the Retail Customer Doc. No. and Sales Date fields on my repair order
A: These fields are located in the Order Information section of the repair order card. Ensure you have the latest version of the Quick Repair extension installed and check that the fields haven't been hidden through personalization.

Q: Can I search for repair orders by Retail Customer Document Number?
A: Yes, you can use Business Central's standard filtering capabilities on the Retail Customer Doc. No. field in the Repair Orders list to find orders with specific customer document numbers.

Q: Why do I need to enter both the document number and sales date?
A: While only the document number has duplicate detection, having both pieces of information provides complete warranty tracking, improves customer service efficiency, and helps maintain accurate cross-references with sales records for comprehensive repair documentation.

Repair Management Setup - Configure number series and system settings
Repair Order Types - Set up repair categorization and billing models
Repair Statuses - Configure repair progress tracking
Repair Solutions - Define standardized repair outcome documentation
Repair Technicians - Register and manage repair technicians
Package Conditions - Set up package condition tracking
External Comment Definitions - Create predefined customer-facing comments
Item Repair Settings - Configure Credit Note Required and repair restrictions on items
Item Repair Solutions - Configure item-specific repair solutions
Extension Setup - Initial configuration of the Quick Repair extension
Getting Started - Quick Repair overview and basic setup

For additional support or questions about Quick Repair, contact BC4All support or consult the community forums.