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

# Entity Types and Properties

> Entity Types and Properties — 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="How do I define entity types in the data model?">
    Entity types are defined in the `domainModelTypes` section of the YAML file using **map format only** — each key is the entity type name, and the value contains its configuration. The `polarionType` property maps the entity type to a Polarion work item type.

    ```yaml theme={null}
    domainModelTypes:
      UserNeed:
        polarionType: user_need
        properties:
          description:
          severity:
      SystemRequirement:
        polarionType: sys_req
        properties:
          description:
          severity:
    ```

    <Warning>
      **Map format only**

      The `domainModelTypes` section must use **map format** (keyed by type name). Array format is not supported and will not work.
    </Warning>
  </Accordion>

  <Accordion title="How do entity type properties work?">
    Each entry under `properties` defines a field exposed in the Powersheet sheet. Properties are listed as keys under the entity type. Key property attributes include:

    | Attribute | Purpose | Default |
    | - | - | - |
    | `name` | Client-facing property name | Required |
    | `serverName` | Polarion field name override | Same as `name` |
    | `customFieldName` | Polarion custom field ID | — |
    | `readable` | Can be read by users | `true` |
    | `updatable` | Can be modified by users | `true` |
    | `scalar` | Single value vs. collection | `true` |
    | `enumValues` | Valid enum option IDs | — |

    Use `serverName` to alias Polarion field names to more user-friendly names, and `customFieldName` when a property maps to a Polarion custom field rather than a built-in field.
  </Accordion>
</AccordionGroup>

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