About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.
Setup steps on this page
Set up Fault symptoms
Use this page to define the symptoms, such as noise or leaks, that workers select when they register a fault on an asset.
Steps from Microsoft
Go to Asset management > Setup > Fault > Fault symptoms.
A short list of observable symptoms such as Noise, Leak, Vibrations, Short circuitLearn uses these as fault symptom examples: what the worker sees or hears, separate from the area and the type of fault.
Renaming a symptom to reuse it for something else. The new name shows on all existing fault registrations, which changes the history.
Solution architect
5Design impact
Can it be undone
Reversible: Names can be changed any time; the change shows on related fault registrations automatically.
If you change it later
You can rename a fault symptom at any time; the new name is shown automatically on the related fault registrations. Microsoft Learn
Technical architect
6Technical
Menu item
EntAssetFaultSymptomChecked in Dynamics 365
Form
EntAssetFaultSymptomChecked in Dynamics 365
Table
EntAssetFaultSymptomShown as “FAULT SYMPTOM” in Record infoKey field: FaultSymptomIdChecked in Dynamics 365
Data entities
EntAssetMaintenanceFaultSymptomEntityAsset management fault symptom Checked in Dynamics 365
Roles to set it up and use it
To set it up or change itMaintenance manager EntAssetMaintenanceManagerTo use itMaintenance clerk EntAssetMaintenanceClerkGive people one of these roles. On this system, 2 roles can open this page.Checked in Dynamics 365