> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nextedy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Assign Configuration to Document

> Link a Nextedy POWERSHEET sheet configuration to a Polarion LiveDoc so that opening the document displays the configured sheet view.

export const LastReviewed = ({date}) => {
  if (!date) return null;
  const formatted = new Date(`${date}T00:00:00Z`).toLocaleDateString("en-US", {
    year: "numeric",
    month: "long",
    day: "numeric",
    timeZone: "UTC"
  });
  return <p className="mt-10 text-sm text-gray-400 dark:text-zinc-500 not-prose">
      Last reviewed on {formatted}
    </p>;
};

## Prerequisites

* At least one sheet configuration created in **Administration > Nextedy Powersheet > Sheet Configurations**
* A data model configured in **Administration > Nextedy Powersheet > Data Models**
* The `nextedySheetConfig` custom field defined for your document type

<Steps>
  <Step title="Create the Custom Field">
    If the `nextedySheetConfig` custom field does not yet exist, create it in Siemens Polarion ALM:

    1. Navigate to **Administration > Documents & Pages > Document Custom Fields**
    2. Decide whether the field applies to all documents or only a specific document type (e.g., `powersheet`, `userNeedsSpec`)
    3. Create a new field with these settings:

    | Property | Value                        |
    | -------- | ---------------------------- |
    | **Id**   | `nextedySheetConfig`         |
    | **Name** | Sheet Config                 |
    | **Type** | Enum: Nextedy - Sheet Config |

    <Frame>
      <img src="https://mintcdn.com/none-17b4493f/KGc-UcQNrDeK-NiS/powersheet/images/48001275923/6.png?fit=max&auto=format&n=KGc-UcQNrDeK-NiS&q=85&s=188008fbf95de7fc8065db7148ca6c4d" alt="custom-fields.xml editor row for the nextedySheetConfig document custom field, with Name 'Sheet Config' and Type set to the Enum 'Nextedy - Sheet Config'" style={{ maxWidth: "720px", width: "100%" }} width="1350" height="376" data-path="powersheet/images/48001275923/6.png" />
    </Frame>

    The enum provider automatically discovers configuration files from both global and project-specific repository locations. Global configurations appear with a `(Global)` suffix in the dropdown. There is no default configuration -- users must explicitly select one.
  </Step>

  <Step title="Assign the Configuration to a Document">
    1. Open the Polarion LiveDoc you want to connect to Powersheet
    2. Open the document properties panel
    3. In the **Sheet Config** field, select the desired sheet configuration from the dropdown

    <Frame>
      <img src="https://mintcdn.com/none-17b4493f/-WiVljKlDztH36bB/powersheet/diagrams/guides/sheet-configuration/assign-config-to-document/diagram-1.svg?fit=max&auto=format&n=-WiVljKlDztH36bB&q=85&s=9b7b1d0c3e8c3631c2004e164895b2e1" alt="diagram" style={{ width: "500px", maxWidth: "100%" }} width="500" height="200" data-path="powersheet/diagrams/guides/sheet-configuration/assign-config-to-document/diagram-1.svg" />
    </Frame>

    The dropdown lists all available configurations:

    * **Project-specific configurations** -- shown by filename without path
    * **Global configurations** -- shown with `(Global)` suffix, ID starts with `/`
  </Step>

  <Step title="Understand Configuration Scopes">
    Powersheet discovers configurations at two levels:

    | Scope   | Repository Location                                                                                         | ID Format       | Use Case                        |
    | ------- | ----------------------------------------------------------------------------------------------------------- | --------------- | ------------------------------- |
    | Project | `.polarion/nextedy/sheet-configurations/`                                                                   | Filename only   | Project-specific layouts        |
    | Global  | Global repository location (see [Configuration Hierarchy](/powersheet/concepts/global-vs-project-specific)) | Starts with `/` | Shared across multiple projects |

    A single sheet configuration can be reused across multiple documents. Each document references the configuration independently through its `nextedySheetConfig` field.

    <Warning title="Configuration must match the data model">
      The sheet configuration references column binding paths that must exist in the associated data model. If you assign a configuration designed for one data model to a document using a different model, columns with unresolvable bindings will fail to display correctly.
    </Warning>

    <Tip title="Start with simple configurations">
      New users should begin with a minimal single-entity configuration and extend incrementally. Jumping directly to complex multi-entity configurations leads to hard-to-diagnose errors. See [Incremental Configuration Approach](/powersheet/getting-started/incremental-configuration) for guidance.
    </Tip>
  </Step>

  <Step title="Edit the Assigned Configuration from the Document">
    Once a configuration is linked to a document, authors can open it directly from the Powersheet toolbar without returning to the administration page. Inside the document, open **Menu > Configuration > Edit Sheet Configuration** to jump straight into the YAML editor for the currently assigned configuration. The same submenu also exposes **Edit Data Model** to reach the associated data model.

    <Frame>
      <img src="https://mintcdn.com/none-17b4493f/KGc-UcQNrDeK-NiS/powersheet/images/48001275923/4.png?fit=max&auto=format&n=KGc-UcQNrDeK-NiS&q=85&s=f4941752ef2c4d81d7143f3fa7ac0e36" alt="Powersheet document Menu dropdown with the Configuration submenu open, exposing Edit Sheet Configuration and Edit Data Model entries" style={{ maxWidth: "720px", width: "100%" }} width="802" height="536" data-path="powersheet/images/48001275923/4.png" />
    </Frame>

    This shortcut is the fastest way to iterate on a configuration while testing it against real data in the document.
  </Step>

  <Step title="Use Template-Based Documents">
    For standardized deployments, you can create **template documents** that already have the sheet configuration pre-assigned. New documents duplicated from the template inherit the configuration assignment, saving administrators from manually assigning configurations for each new document.

    Templates can be duplicated across projects. The configuration and data model are resolved in the target project context.
  </Step>
</Steps>

## Verification

After assigning the configuration and saving the document:

1. Open the LiveDoc in Polarion
2. You should now see the Powersheet table view embedded in the document, displaying columns and data according to your configuration
3. The sheet should load data from the sources defined in the configuration
4. The Powersheet Drive sidebar topic should list your document

## See Also

* [Creating Your First Sheet Configuration](/powersheet/getting-started/first-sheet-configuration) -- build a configuration from scratch
* [Creating Your First Powersheet Document](/powersheet/getting-started/first-document) -- end-to-end document setup tutorial
* [Download Configuration as YAML](/powersheet/guides/sheet-configuration/download-config-as-yaml) -- export an existing configuration for editing
* [Configure Sources](/powersheet/guides/sheet-configuration/configure-sources) -- define data sources within a sheet configuration
* [Incremental Configuration Approach](/powersheet/getting-started/incremental-configuration) -- best practices for building configurations gradually

<LastReviewed date="2026-07-02" />