Hi,
We're about to configure our products and services for field service to start adding them into our incident types and therefore work orders.
The team had already had a go at this and there are around 700 non-inventory products in place. When it comes to services, I understand the process of product creation, using fixed fee fields and price lists. However, it appears field service doesn't really have any product structure/hierarchy in place compared to other non-ms products I've used before.
For example, I've read in the docs that bundles do not work in field service. I've had a go at creating a product family to try and group together a number of services, but this doesn't seem to change anything in product selection or layout.
When assigning products to a work order, I can see that products get filtered down based on the associated price list of the work order which is helpful, but for the technicians adding services/products this can still be a lengthy list.
For context, we service repairs across residential homes, therefore we can have 6 or 7 types of trades, with 100's of incident types and you can imagine the associated services that go with this. Before I start defaulting to using the product title to segregate, is there anything I've missed or should be looking at first?
