| Previous | Next |
| FSRM_E_CANNOT_RENAME_PROPERTY | FSRM_E_MAX_PROPERTY_DEFINITIONS |
FSRM_E_CANNOT_CHANGE_PROPERTY_TYPE
FSRM_E_CANNOT_CHANGE_PROPERTY_TYPE reports an attempt to modify the type of a property definition after it has been committed. Existing file values, rule values, possible values, aggregation, and job conditions are interpreted according to that original type.
Replace the definition safely
- Create a separate property with the required type rather than editing the committed definition.
- Define a deterministic conversion for existing values and reject values that cannot be mapped.
- Update rules and file-management conditions before retiring the old property.
The API explicitly makes the type immutable after commit. Clearing caches or restarting FSRM does not change that schema rule. Also review ordered-list and multi-choice possible values, because a type migration can change aggregation and comparison semantics even when the displayed text looks similar.
Property Type · Property definition · Possible values
Looking for a different code? Search another status or error code.