You can't. This data is a reflection of the input.

Most of the input items have a "hidden" state which you the user can not see or control. For discussion purposes, lets call this state unspecified.

Now, consider the "Seam Welded Check box". For a new job which is initiated as B31.3 (or anything that is not TD/12) you see this checkbox as "grayed out" and other edit boxes as empty. CAESAR II on the other hand sees these fields as unspecified. Unspecified fields are not reported in the input echo.

Now say you change the piping code to TD/12. The "seam welded check box" now must be either checked or not checked. So we change unspecified to "unchecked", and its state appears in the input echo. Once this happens, this item is either checked or not-checked. You can't get back to the unspecified state.