Stop offering a value

Keep the record when it must remain identifiable for older references. The model must provide an availability field or validity dates; these controls do not exist on every type. Read Records.

1. Find and open the record. Check its workspace and whether the change should be immediate in Live or proposed in a change set.
2. If the model provides an availability field, edit it to No and save. In an editable tree, the availability switch or Mark not … menu action can change the same field. The label comes from the model. The record remains, even if a view filters it out.
3. If the type has validity dates, set its end to the first day on which it must no longer be valid. The end is exclusive: an end of 13 December means the last valid day is 12 December. If both dates are present, the end must be later than the start. Save the field.
4. Check the saved value and history, or review and publish the change set when ready. If the record disappears from a filtered view, clear its availability filter to inspect it.

Setting an end date does not schedule publication or remove the record. The browser has no business-date selector for browsing an earlier state; a validity field filter is not a whole-workspace date view. Ask the model administrator if the type offers neither mechanism. Do not delete a record simply because its availability control is absent.

An availability flag does not automatically hide the value from every consuming system. Each system’s agreed reading rules decide whether unavailable records are included. If the record still appears elsewhere, check that agreement with the integration owner rather than deleting the record to make it disappear.