Configuration Tips - Nextedy Documentation

Should I start with a complex or simple data model?

Always start with the simplest possible configuration and extend incrementally. Begin with a single entity type and one or two properties, verify it works in a sheet, then add relationships and additional entity types one at a time. Jumping directly to a complex multi-entity model leads to hard-to-diagnose configuration errors.

Incremental approachStart with one entity type, add a source and a few columns, confirm the sheet loads. Then add a relationship and expand one level at a time. This makes it easy to identify which change introduced a problem.

How does Powersheet know which Polarion link role to use?

The linkRole property in a relationship definition specifies the Polarion link role used to persist the connection. This must match a link role defined in your Polarion project’s link role configuration. The storage property determines how the relationship is persisted — linkedWorkItems is the only supported storage mechanism, using Polarion’s native linking to persist connections.

The constraints section on an entity type restricts which items appear in picker dialogs. You can filter by document location, type, or component:

domainModelTypes:
  SystemRequirement:
    polarionType: sys_req
    constraints:
      pick:
        document:
          moduleFolder: Requirements
          type: requirements_specification
          component: $context.source.document.component

The $context.source.document.component expression dynamically filters results based on the source entity’s document component, enforcing component-scoped relationships. See the Configuration FAQ for more on validation and constraints.