27

If there are Customer Assets that change their location from time to time (cars, ships, lorries, trains, construction machines, ...) it is painful to appropriately plan Work Orders ahead of time for the same Asset but changing locations. When trying to decouple a Customer Asset from the Service Account you're most likely to get an error "The customer asset must be related to the service account of the current work order." when you try to add Work Order Incidents / Service Tasks / Products / Services to the Work Order and want to utilize the OOB Customer Asset field in those Sub-Records. Otherwise, if you're not able to rely on the address provided by the Asset's Account, you would need a custom plugin/async process to overwrite the address on the Work Order. So it would be great if this restriction would be lifted.

Category: Work order
STATUS DETAILS
Completed
Ideas Administrator

Thanks for sharing your feedback. We believe we grasp what you are trying to do; however, to ensure our understanding, please answer the following questions:

  • In this scenario, it sounds like the mobile asset could be treated as a Service Account with an address and geolocation that changes. In what ways are these mobile assets distinct from a Service Account?
  • Does it often cross territories?
  • Can you help us understand why it is treated as a Customer Asset?
  • How far in advance is work scheduled?
  • Can you share any other relevant use-case details that makes enabling associating a customer asset to any service account the best way to manage work on these items?

Jason Cohen

PM, Microsoft