/
Convert Service Requests is dropping the scheduling priority

Convert Service Requests is dropping the scheduling priority

Description of Issue

Adding a scheduling priority when converting a service request does not add the priority code to the work order

Context
  • Enterprise Asset Management 
  • EAM 
Cause

Defect 

Resolution

Install MUN-382457 once it's been released

Workaround:  Use Search to narrow down the servicing department before selecting a service request to convert

Additional Information

This is only happens when:

  • Search is not used to narrow down the servicing department, and
  • The scheduling priority code contains no letters





Related content

Scheduling priority defined on activity code does not default onto work orders created from service requests
Scheduling priority defined on activity code does not default onto work orders created from service requests
More like this
Requests not auto-converting when SRA rule is used
Requests not auto-converting when SRA rule is used
More like this
Selecting Create Work Order in Service Request Inquiry produces a permissions error
Selecting Create Work Order in Service Request Inquiry produces a permissions error
More like this
AR Overhead Charge Codes listed on template are not applied to a work order when converted from a Service Request
AR Overhead Charge Codes listed on template are not applied to a work order when converted from a Service Request
More like this
Assign Work Requests is dropping the Assigned to and Scheduling priority values when a template is added
Assign Work Requests is dropping the Assigned to and Scheduling priority values when a template is added
More like this
Task asset not showing on work orders originating from service requests created in Create Requests program
Task asset not showing on work orders originating from service requests created in Create Requests program
More like this