Fix Model Connection Errors

​

Identify the Error

• Sheet shows a blank area or error dialog on load
• Connection status in Administration > Nextedy Powersheet shows “Failed” instead of “Active”
• Configuration loads but no data appears in the sheet

1

Verify the Model Path in Sheet Configuration

The sources.model property in your sheet configuration must match the name of your data model file. Open your sheet configuration YAML and check the sources section:

sources:
  - model: my-custom-model    # Must match your model file name
    from: UserNeed
    expand:
      - systemRequirements.systemRequirement

The sources.model property must match your custom data model name — not the default rtm. If you created a model named my-project-model, the value must be my-project-model, not rtm or model.

2

Check the Model Path Resolution

Powersheet resolves model paths using these rules:

Model Value	Resolved Path
my-model	{projectId}/my-model (current project)
otherProject/my-model	otherProject/my-model (cross-project)
/my-model	_global/my-model (global scope)

Verify that your model file exists at the resolved path by navigating to Administration > Nextedy Powersheet > Data Models.

If a global model and a project-local model share the same name, the project-local copy takes precedence — the sheet may be reading a different model than you expect, with no error. If you intended to use the global model, check for and remove any project-level copy with the same name. See Troubleshooting FAQ: global vs. project-level configuration for details.

3

Verify Connection Status

Connections go through three lifecycle states:

• Active: Connection is operational and serving data
• Disabled: Connection intentionally turned off by an administrator
• Failed: Connection encountered an error during startup or restart

If the status is Failed, the data model configuration contains an error that prevented initialization.

4

Validate the Data Model YAML

Common data model errors that cause connection failures:

1. Invalid YAML syntax — Check for indentation errors, missing colons, or stray characters
2. Missing domainModelTypes — The root domainModelTypes key must exist
3. Duplicate property names — Entity types cannot have duplicate property names within the same type
4. Invalid polarionType references — Each polarionType must match an existing Polarion work item type

# Correct structure
domainModelTypes:
  UserNeed:
    polarionType: requirement
    properties:
      description:
      severity:

When you save a connection configuration, Powersheet automatically restarts the connection to apply changes. Check the updated status after saving to confirm the fix.

5

Verify Document Binding

Ensure the document is bound to the correct connection. Open the document settings and verify:

• The source references a valid connection ID
• The from field in the source query specifies a valid entity type from the data model

sources:
  - model: my-custom-model
    from: UserNeed              # Must be a domainModelTypes key
    expand:
      - systemRequirements.systemRequirement

Powersheet validates entity configurations server-side. If duplicate property names are detected, an error dialog will appear and the connection will not be created or restarted.

​

Verification

1. Save the data model and sheet configuration
2. Navigate to Administration > Nextedy Powersheet and confirm the connection status shows Active
3. Open the powersheet document
4. You should now see data loading in the sheet without errors

​

See Also

• Validate Your Data Model — comprehensive model validation steps
• Configure Sources — set up source queries and expansion paths
• Creating Your First Data Model — step-by-step model creation
• Fix Type Name Errors — related entity type naming issues