Baseline and Revision Queries - Nextedy Documentation

Revision Query Flow

Revision Parameter

Parameter	Type	Default	Description
`revision`	`integer`	`null`	Document revision number to query. `null` means HEAD (latest). Must be `>= 0`.

URL Parameter

The revision is specified via the _revision URL query parameter:

/polarion/#/project/MyProject/powersheet?_document=Requirements/SystemReqs&_revision=42

Starting with Powersheet 26.7.2, this is the underscore-prefixed system parameter Powersheet generates. The older bare revision name is still honored as a legacy alias, so existing links keep working.

Value	Behavior
Not specified	Shows latest data (HEAD)
`0` or positive integer	Shows data at the specified revision

Setting Revision Programmatically

The revision can be changed without a full page reload. The URL parameters are updated and the data is re-fetched at the new revision.

Revision PickerUse the revision picker in the Powersheet UI to navigate between document revisions. Pass undefined to clear the revision and return to HEAD.

Read-Only Mode

Historical revisions are always displayed in read-only mode. The sheet enters read-only mode when any of these conditions is true:

Condition	Description
`revision` is set	Viewing a historical revision
`config.isReadOnly` is `true`	Configuration flag forces read-only
User has `readOnly` permission	Permission-based restriction

No Editing on Historical RevisionsWhen viewing a historical revision, all editing operations (cell editing, row creation, row deletion, save) are disabled. The sheet displays data as it existed at the specified revision.

Query Execution with Revision

The query processor handles revisions at two levels:

1. Query Parameter Revision

The revision parameter in the entity query controls which historical version of the data is queried:

Parameter Source	Priority	Description
Query parameter `revision`	Highest	Explicitly set on the query
Context baseline	Lower	Inherited from the query context baseline

2. Configuration Processing

When a revision is active, the configuration processor:

Injects the revision parameter into the main data source query
Appends the revision number to the document display name (e.g., SystemReqs (Rev 42))
Sets the sheet to read-only mode

Document Context with Revision

Property	Type	Description
`document.full`	`string`	Full document path (`folder/name`). Does not change with revision.
`document.folder`	`string`	Document folder/space component
`document.name`	`string`	Document name component
`revision`	`integer`	Current revision number, or `null` for HEAD

The document display name includes the revision when viewing historical data:

SystemReqs (42)

Configuration at a Revision

The sheet configuration is not read at the revision. The configuration request carries only the project and the document, and is served from the current revision of both the document and the configuration file. The data model is likewise read at its current revision. The configuration URL includes a timestamp only so that the browser does not serve a cached copy.

Entity Metadata at Revision

Entity query results at a specific revision include standard metadata fields:

Field	Type	Description
`objectId`	`string`	Unique entity identifier
`id`	`string`	Polarion work item ID
`title`	`string`	Work item title at the specified revision
`updated`	`datetime`	Last modification timestamp at or before the revision
`projectId`	`string`	Project foreign key

Baseline vs. Revision

Concept	Description
Revision	A specific SVN revision number representing a point in the project’s history
Baseline	A named project baseline that maps to a specific revision number

The query processor supports both approaches. The revision can come from an explicit query parameter or from a project baseline associated with the query context.

Verify in applicationThe relationship between Polarion project baselines and SVN revision numbers depends on your Polarion server configuration. Consult your administrator for baseline-to-revision mapping.

Complete YAML Example

sources:
  - id: requirements
    title: System Requirements
    model: rtm
    query:
      from: UserNeed
      where: "type = 'UserNeed'"
    constraints:
      applyCurrentDocumentTo: UserNeed
    expand:
      - name: systemRequirements
        title: System Requirements
        expand:
          - name: systemRequirement

columns:
  id:
    width: 80
    sort: asc
  title:
    width: 300
    hasFocus: true
  systemRequirements.systemRequirement.title:
    width: 250
  systemRequirements.systemRequirement.severity:
    width: 100

When this configuration is loaded with ?_revision=42 in the URL, the query processor:

Fetches UserNeed entities as they existed at revision 42
Expands systemRequirements.systemRequirement at the same revision
Displays the sheet in read-only mode
Shows the document name with revision suffix

Query Context — query parameter reference
Collection-Scoped Sheets — open a sheet with a revision per document instead of one revision for the whole sheet
EntityQuery — query structure and parameters
Document Filtering — document-level query constraints

​Revision Query Flow

​Revision Parameter

​URL Parameter

​Setting Revision Programmatically

​Read-Only Mode

​Query Execution with Revision

​1. Query Parameter Revision

​2. Configuration Processing

​Document Context with Revision

​Configuration at a Revision

​Entity Metadata at Revision

​Baseline vs. Revision

​Complete YAML Example

​Related Pages

Revision Query Flow

Revision Parameter

URL Parameter

Setting Revision Programmatically

Read-Only Mode

Query Execution with Revision

1. Query Parameter Revision

2. Configuration Processing

Document Context with Revision

Configuration at a Revision

Entity Metadata at Revision

Baseline vs. Revision

Complete YAML Example

Related Pages