Skip to content

Environments Tab

The ENVIRONMENTS tab manages which environments this resource instance is mapped to and the primary key value that identifies it in each one.

Edit Resource — Environments

Targeted Environments

The TARGETED ENVIRONMENTS section lists all environments configured for this profile as a checklist.

Element Description
Select All Checkbox at the top to select or deselect all environments at once
Environment row Environment name + colored badge (e.g., Development, SIT)
MASTER badge Marks the master environment — the reference used for cross-environment ASBO grouping
Primary Key Values Panel that expands when an environment is checked. Displays the PK attribute name and data type as badges, with an input field for the PK value of this instance in that environment

To manage mappings:

  • Check an environment to add a mapping and enter its PK value
  • Uncheck an environment to remove its mapping
  • Edit the PK input field directly to correct or update the primary key value

Why PK values differ per environment

The same logical business object often has a different internal identifier in each environment (Development, QA, Production). BizMetry uses the PK value per environment to correctly identify and group telemetry frames from that environment back to this resource instance.

Manually Created Resources

For resources created manually via + New Resource, the Primary Key Values panel contains only the PK input field. The value must be typed in directly.

Database-Imported Resources

For resources imported from a datasource, the Primary Key Values panel shows two additional controls alongside the PK input field:

Edit Resource — DB Controls

Control Description
Pick from Database Opens the DB Picker — a live browser of the actual records in the datasource table, allowing you to remap this resource to a different record
Record Viewer Opens the Record Viewer — a read-only view of the database record currently mapped to this resource in this environment

These controls are only available when the environment has an active datasource connection configured.