Visit snapshot denormalization for audit traceability
Key Takeaway
Visit Snapshot is built in and needs no configuration. At signature capture and again at visit report submission, it copies values such as license statuses and product batch numbers into the visit, so auditors see what applied at the time of the visit.
Visit Snapshot, which Salesforce also calls denormalization, copies key account, license, and product values into the visit record at the moment the visit is finalized. Its purpose is compliance and auditing. The visit keeps a permanent record of what was true when the rep signed or submitted it, even if values in the source records change later. A license status and a product batch number are examples of such values.
What the snapshot stores
Visit Snapshot preserves the exact state of account, license, and product data at the moment a visit is finalized, so auditors can see the values that applied to that interaction. The system reads values from the records the visit looks up to. It stores those values as static text in AdditionalInformation fields on the Provider Visit object and its child objects.
Because the values are static text, the snapshot works like a printed receipt rather than a live link. After the values are written, they stay as they were, even when the source record changes.