Validating and Saving Configuration Files
- Updated2026-07-08
- 1 minute(s) read
Validating and Saving Configuration Files
The Configuration Utility validates continuously and enforces validity when you save a file.
The Configuration Utility provides the following validation checkpoints:
- Fields are checked as you type, with green/yellow/red indicators.
- Errors (red) are schema violations. This includes issues such as missing required values, out-of-range numbers, and invalid choices. Errors prevent saving.
- Warnings (yellow) are informational. This includes issues such as an empty metadata field or an unknown key. Warnings do not prevent saving.
The following rules are enforced when you save a file:
- If any attenuators are still Unassociated, the save is blocked and the Configuration Utility tells you how many unassociated attenuators remain. Assign or remove them, then save again.
- The file is validated. If there are errors, the save is blocked and a dialog lists each error with its section, key, and message.
- If validation passes, the file is written to disk.