/
Asset location codes not defaulting onto service requests
Asset location codes not defaulting onto service requests
Description of Issue
Asset location codes not defaulting onto service requests generated from Create Requests and Service Request Quick Entry
Context
Tyler EAM
Cause
Resolution
Install the appropriate work ticket for your version once it's been released:
- 2019.1.20.0 - MUN-398207
- 2019.1.21.0 - MUN-398449
- 2019.3.16.0 - MUN-398450
- 2020.1.0.0 - MUN-398451
- 2020.2.0.0 - MUN-398452
- 2020.3.0.0 - MUN-398453
- 2021.1.0.0 - MUN-398236
Workaround: Use Service Requests to generate requests
Additional Information
, multiple selections available,
Related content
Service Request Quick Entry drops asset and address from service request
Service Request Quick Entry drops asset and address from service request
More like this
Requests created from Create Requests are missing facility asset addresses
Requests created from Create Requests are missing facility asset addresses
More like this
Service Request program auto populates the Asset Code into the Location Code field upon creation
Service Request program auto populates the Asset Code into the Location Code field upon creation
More like this
Asset addresses and location codes do not default onto work order
Asset addresses and location codes do not default onto work order
More like this
Create Requests program does not display assets correctly when filtering drop down
Create Requests program does not display assets correctly when filtering drop down
More like this
Geo Code does not default onto work order
Geo Code does not default onto work order
More like this