How Service Advisers Are Managed
Source: service_advisers_controller.rb
- Service adviser records use an upsert pattern on save: existing records are updated, new records are created
- A service adviser cannot be deleted if they have associated inspections — the inspections must be reassigned or removed first
- Adviser codes must be unique across the company; duplicate codes are rejected at validation
- Search matches against first name, last name, or the combined full name, so partial name searches work
Support scenarios
- "I can't delete a service adviser" → The adviser has inspections linked to them. Reassign or remove those inspections before deleting the adviser.
- "I get a duplicate error when creating a service adviser" → Adviser codes must be unique. Another adviser (possibly inactive or deleted) may already have that code. Check all advisers including inactive ones.
- "Search isn't finding the service adviser" → Search matches first name, last name, or full name. Try searching by just the first name or just the last name if the full name search isn't working.