Calculated asset fields

We strongly support this feature.

In enterprise environments, calculated or derived fields are not just a convenience feature, but a fundamental data governance control.

In our use case, the mandatory primary “Name” field must remain consistent across asset types (contacts, organizations, etc.). We already store structured data such as:

•   First Name•   Last Name•   Organization Name•   Legal Name

Without calculated fields, we are forced to rely on manual entry or external API automation, which increases entropy and introduces data inconsistency risks.

Having the ability to:

•   Define formulas (e.g., First Name + “ “ + Last Name → Name)•   Make fields read-only and driven by structured fields•   Apply basic transformation logic (concatenation, conditional rules, formatting)

would significantly improve data quality, naming consistency, and compliance with governance models.

At scale, this becomes essential for maintaining reliable asset inventories.

We would strongly encourage prioritizing this capability.