To improve performance and manage your resources efficiently, you can
choose not to take history snapshots when you develop data types. Every time a value in
a data type changes, before you implement the change, the system takes a snapshot of the
previous instance in case you need to restore the data type to the previous state. With
multiple changes, omitting the snapshot can save you time and resources.
example, you can choose not to take the snapshot of a data type in the following scenarios:
- A data type is only an additive and remains unchanged throughout your entire
- The frequency of updates to a data type is large, which makes snapshots less
- Because every snapshot is a BLOB write, high numbers of snapshots might affect
- You implement your custom history-saving policy.
The system stores snapshots in the History- class of a
respective data type.Note: You can omit snapshots only for data types. When you
develop rules, the system takes snapshots and stores them in a related
Result: When a value in a data type changes, the system does not
take the snapshot of the initial value.
- In the navigation pane of Dev Studio, click Data types.
- Hover over a data type, and then click .
- On the data type rule form, click the Advanced
- In the Bypass History on Save section, select
- Click Save.