Skip to content

Manage records with the dynamic data management page

Overview

The dynamic data management page is a reusable record-management screen that handles many different object types in a single, consistent interface. Instead of creating a custom page for every object, the application loads the collection you request and builds the table, labels, and available actions from that collection’s metadata.

You can open a direct link to a specific collection and immediately start reviewing records in a familiar layout. The page title, description, and table columns change to match the collection you opened.

This page requires a signed-in user and a collection identifier in the URL. If the identifier is missing or the requested collection definition cannot be loaded, the page shows an alert and does not continue.

When to use this

Go here when you already know which data set you need to work with and want a fast list view for reviewing, searching, and updating those records.

  • Review records for a specific collection in a table
  • Use or share direct links that open a precise collection
  • Get a consistent admin-style experience across many object types
  • Scan, search, or inspect records quickly
  • See object-specific columns without learning a new page for every dataset

How it works

The page opens a specific collection identified by the cid query parameter in the URL. The cid tells the app which object or collection to load, so bookmarks and shared links land users directly in the intended list.

If cid is missing the page shows an alert and does not proceed.

Sign-in comes first

You must be signed in before the page loads collection data. If your session has expired or you open the page while signed out, you will be prompted to authenticate before working with records.

The page builds itself from collection metadata

After identifying the collection, the page loads its collection definition (metadata) and builds the interface from that information. The metadata supplies:

  • The collection label shown on the page
  • Any collection description
  • The fields used as table columns
  • Row layout and field formatting

The page uses cached metadata when available and fetches metadata if needed. If the collection definition cannot be loaded, the page shows an alert and stops.

Columns change by object type

Table columns are generated from the selected collection’s field definitions. For many standard collections, the page includes Name and Description columns to make lists easier to read. Lookup-style collections may use a different column set.

Review rows and take action

The main working area is the record table. From there you can review rows, scan values, search for records, and open row-specific actions. Depending on the collection and your access, the page can open a record detail view or action menu without leaving the list.

Typical workflow

  1. Sign in to the application.
    Ensure your session is active before opening the page. If you open a bookmarked link while signed out, authenticate when prompted.

  2. Open the direct link for the collection you need.
    The link must include the cid query parameter so the page knows which collection to display.

  3. Confirm the page title and description.
    Check the title and any description to make sure you opened the intended collection before making changes.

  4. Scan the table structure.
    Review the visible columns to understand what the collection tracks (ownership, status, descriptive attributes, reference values, etc.).

  5. Search or browse for the records you need.
    Use the search box to narrow the view on large lists, or scan rows directly for smaller sets.

  6. Open row actions or the record detail view.
    Use the row action menu or detail panel to inspect or act on a record without losing your place in the list.

  7. Repeat the workflow for another collection.
    Switching to a different collection is straightforward—open its link and continue from the same pattern.

Fields, controls, and options you may see

Item What it does Notes
cid in the URL Chooses which collection the page loads Required
Page title Shows the current collection name or label Changes by collection
Collection description Gives context for the selected collection Shown when available
Record table Lists records for the current collection Main work area
Name column Common identifying field in many lists Usually present for standard objects
Description column Common summary field in many lists Usually present for standard objects
Search box Narrows the visible records Useful for larger collections
Row action menu Opens actions for an individual record Actions vary by collection and permissions
Detail panel Opens a record in a side panel or modal-style view Available for supported record views

Automation and integrations

The page automatically loads the collection metadata, builds the table columns from that setup, and presents a consistent interface across object types. If your organization uses broader automation (data imports, downstream processes, external integrations), those workflows can affect what records appear here and what actions are available on a record.

Things to watch for

  • You must be signed in. The page will not continue when you are unauthenticated.
  • The link must include the cid query parameter. Without it, the page will alert and stop.
  • Collections can look different. Columns are driven by the collection’s field setup.
  • Some collections do not include Name and Description; lookup-style collections use different layouts.
  • If the collection metadata cannot be loaded, the page shows an alert instead of a partial view.
  • Available row actions and detail views vary by collection and by your access level.
  • Verify the page title before performing bulk or destructive actions.