Skip to main content

​
Identify the Error

Relationship errors occur when the relationships section of your domain model YAML contains invalid references or incompatible settings. Common symptoms include:
  • Connection fails to start after saving the domain model
  • “Left error” or “right error” messages in the server log
  • Navigation columns appear empty or fail to expand
  • Expansion paths in the sheet configuration produce no results

​
Step 1: Verify Entity Type References

Every relationship must reference valid entity type names in its from and to fields. These must match keys defined under domainModelTypes: 
domainModelTypes:
  UserNeed:
    polarionType: requirement
  SystemRequirement:
    polarionType: systemRequirement

relationships:
  - from: UserNeed                # Must match a domainModelTypes key
    to: SystemRequirement         # Must match a domainModelTypes key
    cardinality: one-to-many
    storage: linkedWorkItems
    linkRole: has_parent
    direct:
      name: systemRequirements
    back:
      name: userNeed
When you see a “left error”, the from entity type name is invalid or missing from domainModelTypes. A “right error” means the to entity type is invalid. Always check that from/to values exactly match your entity type keys, including capitalization.

​
Step 2: Check the Error Mapping

Use this table to quickly identify the source of relationship errors:
Error SignalCauseFix
”left error”Invalid from entity typeCorrect from to match a domainModelTypes key
”right error”Invalid to entity typeCorrect to to match a domainModelTypes key
Empty navigation columnMissing direct.name or back.nameAdd navigation property names
Expansion path failsNavigation name mismatchAlign expand path with direct.name/back.name
Link not persistedWrong linkRoleMatch linkRole to a Polarion link role ID

​
Step 3: Use Correct Navigation Property Names

The direct.name and back.name fields create navigation properties on the source and target entity types. These names are used in column binding paths and expansion paths: 
relationships:
  - from: UserNeed
    to: SystemRequirement
    cardinality: one-to-many
    storage: linkedWorkItems
    linkRole: has_parent
    direct:
      name: systemRequirements      # Forward: UserNeed -> SystemRequirement
    back:
      name: userNeed                 # Reverse: SystemRequirement -> UserNeed
The sheet configuration expansion path must match these navigation names: 
sources:
  - from: UserNeed
    expand:
      - systemRequirements.systemRequirement    # Matches direct.name
diagram The linkRole must match a link role defined in your Polarion project configuration. Check Administration > Work Items > Link Roles in Polarion to confirm the link role ID exists. 
linkRole: has_parent    # Must match a Polarion link role ID
The linkRole value is the link role ID (e.g., has_parent), not the display name (e.g., “Has Parent”). Check the Polarion administration interface for the exact ID string.

​
Step 5: Validate Cardinality

Ensure the cardinality value matches the actual relationship between your entity types:
CardinalityMeaningColumn Behavior
one-to-oneSingle entity each directionSingle-value cell
many-to-oneMany source to one targetSingle-value cell
one-to-manyOne source to many targetsMulti-item display
many-to-manyMany on both sidesMulti-item with linking mode

​
Verification

After correcting the relationship configuration:
  1. Save the domain model
  2. Confirm the connection restarts to Active status
  3. Open the powersheet document and expand a row with related entities
  4. You should now see child entities appearing correctly under the expansion path

​
See Also

Sources: model.yaml, riskmanagement_model.yaml, sf_model.yaml, DomainModelV2.java, ticket insights
Support TicketsSource Code
  • DomainModelV2.java
  • model.yaml
  • riskmanagement_model.yaml
  • sf_model.yaml
  • prod-powersheet-src/com.nextedy.powersheet.client/cypress/fixtures/models/constraints-base.yaml