Skip to main content

Field Constraints

This guide describes data types, required fields, uniqueness, and validation rules common to Cloudaware’s namespaced sObjects. Exact constraints can vary by object and package version.

Types and Limits​

Cloudaware CMDB fields use standard Salesforce field types and Cloudaware-specific conventions. Common field types include:

  • Text: typically 80–255 characters for identifiers and names
  • Text Area (Long): length can range from 256 to 131,072 characters; typically used for descriptions
  • Text (Encrypted): up to 175 characters for combinations of letters, numbers, or symbols
  • Number: precision set/scale per field (e.g., sizes, costs, utilization)
  • Checkbox: state flags (e.g., encrypted, public)
  • Date/DateTime: lifecycle, creation, expiration timestamps
  • Picklist: normalized enumerations (e.g., resource states)
  • Reference: lookup/master‑detail fields to related objects
  • Structured blobs: JSON‑like fields for tags/labels and configuration snapshots
note

Adhere to Salesforce limits for field types.

Required fields​

Required fields vary by object. Most CMDB objects define required identity and scoping fields, commonly including:

  • Provider unique ID and/or Cloudaware UUID CA10__caUuid__c.
  • Owning container, such as an account, subscription, project, tenant, or cluster, via lookup.
  • Location fields, such as region, zone, namespace, or data center, where applicable.

Master‑detail relationships are implicitly required on the child.

Uniqueness and Keys​

  • Natural keys often combine provider ID + account/subscription + region/zone.
  • Cloudaware maintains stable identifiers for deduplication across discovery runs.
  • Some fields are marked External ID or Unique. Use these fields for idempotent upserts where supported.

Validation and Normalization​

  • Tag and label keys may be normalized for case, formatting, and provider-specific conventions.
  • Units may be normalized, such as GiB versus GB, in calculated or normalized fields.
  • Date, time, region, account, and provider values may be standardized to support cross-cloud reporting.
  • Certain fields participate in platform indexes. Prefer indexed or selective fields when building filters, reports, and integrations.

Soft‑Delete and Retention​

  • CA10__disappearanceTime__c indicates the record has departed the source; use = NULL to filter active data.
  • Historical retention is controlled by organization policies and Cloudaware configuration. Design reports, dashboards, and jobs to exclude disappeared records unless historical or decommissioned assets are required.
  • Deleted or disappeared records may still appear in CMDB for audit, history, or lifecycle analysis, depending on retention settings.