Skip to content

Virtual fields and encrypted fields

Concept5 minExpert

Before you start

Most fields keep their value in a column of the module, exactly as typed. Two switches under Storage in the field editor change that. Virtual field keeps nothing and works the value out when it is needed. Encrypt values keeps the value, but encrypted.

The Storage section of the field editor for Contract Value, with the Virtual field and Encrypt values switches, both off.
    Virtual field: computed at display time and not stored in the database.
    Encrypt values: values are encrypted at rest.

What is a virtual field?

Section titled “What is a virtual field?”

A virtual fieldVirtual fieldA field computed at display time and not stored.Open glossary ↗ has no stored column. Use it with a Smart field: when records load, Beezr runs the Smart Script and puts the result in the record. See Calculate a value with a smart field.

An insight field is a virtual smart field. Beezr turns the switch on for you when you save one.

Choose virtual when the value comes from a script and should reflect other records each time it is shown. Choose a normal smart field when you report on the value, because analytics queries read the stored value. Decide when you create the field, and switch Virtual field on in the new-field editor.

A virtual smart field runs for every record that loads, so keep its script short.

What is an encrypted field?

Section titled “What is an encrypted field?”

An encrypted field keeps its value in the module, encrypted with a key you choose. It suits values people read on the record, such as an ID number or a bank detail.

To use it you need three things:

  • A workspace set up for field-level encryption. Contact support or your success manager to set it up.
  • An encryption key with the status ACTIVE. Create keys under Account settings › Users & Security › Encryption Keys, then pick one in the Encryption key list.
  • A decision at creation. Switch Encrypt values on in the new-field editor and pick the key there.

Keep the key active for as long as the field is in use. Plan a data migration before you change encryption keys on a field that already holds data.

Which should I choose?

Section titled “Which should I choose?”
Normal fieldVirtual fieldEncrypted field
What Beezr storesThe valueNothingThe value, encrypted
Works withEvery typeSmart fieldsAn ACTIVE encryption key
Choose it whenMost of the timeThe value comes from a script and reflects other recordsThe value is sensitive and people read it on a record
Decide itAny timeWhen you create the fieldWhen you create the field

Check yourself

Which of these values is stored in the module's database?
Show the answer

A smart field with Virtual field switched off. A virtual field has no stored column. Beezr saves an insight as a virtual smart field.

When do you switch on Encrypt values for a field?
Show the answer

When you create the field. Decide on encryption in the editor when you create the field, and choose an active encryption key there.

What's next

Track value changes in record historySwitch on Track value changes for a Lookup field, such as a status, so Beezr keeps the old value, the new value, who changed it and when.The key field and the record headerUnderstand the key field that Beezr creates with every module, and how the In header setting and Position build the top of a record page.

Last checked