(((This article applies to a new version of audit)))

When you define the fields that are recorded in the audit, take into account visibility [Definition-submission

submission].

For example, there are fields «Name»,» «Name, middle name «and» calculated field» «name. Calculated field has signified, required all fields in the view, however, that the audit was only» «name, is enough to make the field «Name»,» «Name, middle name» «invisible at the level of ideas.

(((For information about changing the master did not get into auditing, you should make invisible all the fields in the wizard. The invisibility of datalow in performance is also considered.)))

((( Because when writing audit data, only the values of fields from a formed object, for the correct recording of data on a calculated field not [definition DataServiceExpression](fo_not-stored-attributes.html), but also required [duplicate calculations in get'Tere properties](fo_not-stored-attributes.html).)))