Use trades to group services
Trades let you group incident types in your preferred way. Configure trades and trade coverages to simplify the creation of work orders and the services that are provided in a functional location or for a service account, or for accounts at locations. Using trades adds another layer of details to create reports and filter charts on reports.
Prerequisites
An administrator must enable Trades.
Create trades
Before you can map incident types to a trade, an admin must define the trades that are available for your business.
- Go to Settings > General > Trades.
- Select New.
- Choose the Type for the trade. Choosing Coverage defines the account or functional location that a trade covers. Exclusion removes trade coverage for the account or functional location.
- Name the trade and Save it.
Map trades to incident types
To group incident types by trade and create reports based on trades, an admin must configure the mapping. An incident type can map to one trade only.
- Go to Settings > Work Orders > Incident Types.
- Open the incident type record you want to map to a trade.
- On the Details tab, choose the value in the Trade field.
Configure trade coverages
Trade coverage defines which trades are covered for an account or a location to ensure the right level of service is provided. For example, if a location doesn’t have air conditioning, it shouldn’t be possible to create an incident related to the AC (air conditioning) system for that location. The same logic applies to accounts if the service contract doesn’t include HVAC (heating, ventilation, and air conditioning) maintenance.
- Go to Settings > General > Trade coverages.
- Select New.
- Choose a trade and select an account, a functional location, or both.
- Save the trade coverage.
Alternatively, you can also show Trade Coverage as a related entity to your Accounts and configure trade coverage from there. That way you can see trade coverage with your service accounts and the trade coverage is automatically mapped to the right account.
Trade coverage example
Trade coverage
Account | Trade | Location | Type |
---|---|---|---|
Contoso | Plumbing | - | Coverage |
Contoso | HVAC | Washington | Coverage |
- | Plumbing | California | Coverage |
- | Roofing | Nevada | Coverage |
Contoso | Roofing | Nevada | Exclusion |
Work order
Account | Trade | Location | Validation | Reason |
---|---|---|---|---|
Contoso | Plumbing | Arizona | Covered | Plumbing for Contoso isn't restricted to a functional location. |
Contoso | Roofing | Washington | Not covered | Roofing for Contoso has no trade coverage defined. |
Contoso | HVAC | Seattle | Covered | HVAC for Contoso is covered in Washington state and Seattle is in Washington state. |
Northwind Traders | Plumbing | San Francisco | Covered | Plumbing is covered regardless of the service account in California and San Francisco is in California. |
Northwind Traders | Roofing | Los Angeles | Not covered | Roofing, regardless of the service account, is only covered in Nevada. Los Angeles is in California. |
Contoso | Roofing | Las Vegas | Not covered | Roofing for Contoso has an exclusion defined for Nevada. Las Vegas is in Nevada. |
Next steps
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for