Skip to main content

​
Identify the Error

Type name errors occur when the domain model contains entity type names that violate naming rules. Symptoms include:
  • Connection status shows Failed after saving the domain model
  • Error messages referencing unrecognized type names
  • Sheet configuration from field fails to match any entity type

​
Step 1: Check Entity Type Naming Rules

Entity type names in domainModelTypes must follow strict rules:
RuleValidInvalid
Single word, no spacesSystemRequirementSystem Requirement
No special charactersUserNeedUser-Need, User_Need
PascalCase recommendedDesignRequirementdesignrequirement
Must be uniqueOne Hazard entryTwo Hazard entries
# CORRECT - single word PascalCase names
domainModelTypes:
  UserNeed:
    polarionType: requirement
  SystemRequirement:
    polarionType: systemRequirement
  DesignRequirement:
    polarionType: designRequirement

# INCORRECT - spaces and special characters
domainModelTypes:
  User Need:              # Space in name
    polarionType: requirement
  System-Requirement:     # Hyphen in name
    polarionType: systemRequirement
Domain model entity type names must be single words without spaces or special characters. This is a strict validation rule — names with spaces will cause the connection to fail silently without a clear error message.

​
Step 2: Distinguish Entity Type Names from Polarion Type IDs

A common mistake is confusing domain model entity type names (the YAML keys under domainModelTypes) with Polarion work item type IDs (the polarionType value): diagram The polarionType maps your domain model entity to a Polarion work item type, but all references within the domain model (relationships, queries, sources) use the entity type name (the YAML key).

​
Step 3: Fix Relationship References

When relationship from and to fields reference an invalid entity type name, you may see “left error” or “right error” messages:
  • “left error” = the from entity type name is invalid
  • “right error” = the to entity type name is invalid
relationships:
  - from: UserNeed              # Must match a domainModelTypes key
    to: SystemRequirement       # Must match a domainModelTypes key
    cardinality: one-to-many
    storage: linkedWorkItems
    linkRole: has_parent
The from and to values must exactly match the keys under domainModelTypes — including capitalization. systemRequirement (lowercase s) will not match SystemRequirement (uppercase S).

​
Step 4: Fix Source Query References

The from field in your sheet configuration sources must also use the entity type name: 
sources:
  - model: my-model
    from: UserNeed    # Entity type name, NOT "requirement" (Polarion type ID)
    expand:
      - systemRequirements.systemRequirement

​
Verification

After correcting type names:
  1. Save the domain model configuration
  2. Check that the connection status returns to Active
  3. Open the powersheet document
  4. You should now see data loading correctly with no type-related errors in the sheet

​
See Also

Sources: Ticket insights (type naming rules), ConfigProvider.tsx, admin.cy.ts
Support TicketsSource Code
  • HttpErrorInfo.java
  • prod-powersheet-src/com.nextedy.powersheet.client/src/modules/ConfigProvider/ConfigProvider.tsx
  • prod-powersheet-src/com.nextedy.editor/src/types.d.ts
  • ServerRenderer.java
  • prod-powersheet-src/com.nextedy.powersheet.client/cypress/e2e/admin/admin.cy.ts