> ## 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.

# Configuration Tips

> Configuration Tips — common questions about Nextedy POWERSHEET.

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

<AccordionGroup>
  <Accordion title="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.

    <Tip>
      **Incremental approach**

      Start 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.
    </Tip>
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="How do picker constraints filter related entities?">
    The `constraints` section on an entity type restricts which items appear in picker dialogs. You can filter by document location, type, or component:

    ```yaml theme={null}
    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](/powersheet/faq/configuration) for more on validation and constraints.
  </Accordion>
</AccordionGroup>

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