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

# Fix Column Configuration Issues

> Read the configuration issues a Nextedy POWERSHEET sheet reports, and fix each kind of problem in the sheet configuration.

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>;
};

A sheet that opens with a chip counting configuration issues in the bar above it has loaded some of its columns and left the rest out. This guide takes you from that chip to a configuration that loads every column.

## Prerequisites

* A sheet that opens with a configuration issues chip in the bar above it.
* Permission to edit the sheet configuration, if you intend to make the fix yourself. Without it, you can still read and copy the details and pass them to whoever set the sheet up.

## Identify the Error

<Steps>
  <Step title="Open the issues panel">
    Select the chip in the bar above the sheet. It states how many problems the configuration has, and whether the sheet has been made read-only because of them.

    The panel opens listing one row per problem, each naming the column it belongs to. It is closed when the sheet loads, so nothing has been read for you -- opening it is the first step.
  </Step>

  <Step title="Read each problem">
    Expand a row to see the reason in plain language, and -- where they add something -- a hint at what to change and the technical detail the sheet recorded while loading that column. A problem whose own message is already written for a configuration author is shown once, as the reason, with nothing repeated underneath.

    When there are three problems or fewer every row is already expanded. Above three, the first row is expanded and the rest are yours to open -- so you can see the shape of the list before reading into it.
  </Step>

  <Step title="Copy the details if someone else will fix it">
    **Copy details** puts the whole report on the clipboard: a summary line saying how many of the configured columns failed, then one line per problem with the column name, the reason, the hint and the technical detail. Paste it into the message you send to whoever maintains the sheet.
  </Step>

  <Step title="Open the sheet configuration">
    If you are allowed to configure the sheet, the panel offers **Edit Sheet Configuration**, which opens the configuration in a new browser tab. Your unsaved work in the sheet is left alone.

    If the panel tells you to ask the person who set the sheet up, you do not have that permission, and step 3 is your route. The button can also be absent because the page hosting the sheet does not supply a link to the configuration; in that case reach the configuration through **Administration > Nextedy Powersheet > Sheet Configurations** instead.
  </Step>
</Steps>

## Fix Each Kind of Problem

<Steps>
  <Step title="A field that does not exist">
    The reason names the field the column asked for and the type it looked on. Either the field name is misspelled, or the column is pointed at the wrong type.

    Correct the spelling, or point the column at a field that does exist on that type. The [Model Helper Widget](/powersheet/guides/customization/use-model-helper) lists the properties each type actually carries.
  </Step>

  <Step title="A path that cannot be followed">
    The reason names the step in the path that failed. That step is not a link to another work item, so the path stops there and the rest of it is unreachable.

    Walk the path one step at a time against the data model and check that every step but the last is a relationship. See [Navigation Properties](/powersheet/concepts/navigation-properties) for how a path is resolved.
  </Step>

  <Step title="Settings the sheet rejected">
    The reason here is the message from the part of the sheet that rejected the column -- it names what it could not accept. Where a rejection has a chain of causes behind it they are shown on one line, outermost first, separated by arrows; read left to right to get from the symptom to its cause.

    Compare the column against the [Sheet Configuration Reference](/powersheet/reference/sheet-config/index) and correct whatever the message names.
  </Step>

  <Step title="Two columns showing the same field">
    The reason names the column that was kept. The one being reported is the later of the two, and it was dropped.

    Either remove one of the two, or point the reported column at a different field. A duplicate does not make the sheet read-only, so this one can wait -- but the column will stay missing until it is resolved.

    <Tip>
      **Two columns, one field, on purpose?**

      If you genuinely want the same field twice -- a value and a formatted variant, say -- give the second column its own binding rather than repeating the first. Powersheet keeps only the first column for a given binding.
    </Tip>
  </Step>
</Steps>

## Verification

<Steps>
  <Step title="Save the configuration and reload the sheet">
    Powersheet does not pick up configuration changes while a sheet is open, so save your change and then reload the Polarion document page -- see [Why don't my configuration changes take effect?](/powersheet/faq/troubleshooting/configuration-issues).
  </Step>

  <Step title="Confirm the chip is gone">
    A configuration with no failing column shows no chip at all. If a chip is still there, open it -- the count will have dropped, and the rows that remain are the ones still to fix.
  </Step>

  <Step title="Confirm the sheet accepts edits again">
    A sheet that was read-only because of the configuration returns to normal once the last problem other than a duplicate is fixed. Check that the save control and the edit menu are available again.

    If the sheet is still read-only with no issues reported, the cause is something else -- see [Loading and Display Issues](/powersheet/faq/troubleshooting/loading-and-display-issues).
  </Step>
</Steps>

<Warning>
  **A sheet that shows no grid at all**

  If every column in the configuration fails, there is no sheet to display. Instead of a grid you get a message saying the sheet cannot be displayed and how many columns were configured, and there is no chip to open. Work from the configuration itself -- start with the data model the sheet reads from, since a wrong model makes every column fail at once. See [Fix Model Connection Errors](/powersheet/guides/troubleshooting/fix-model-connection-errors).
</Warning>

## See Also

* [Column Configuration Diagnostics](/powersheet/concepts/column-configuration-diagnostics) -- What is detected, and why a configuration problem locks the sheet
* [Debug Custom Field Issues](/powersheet/guides/troubleshooting/debug-custom-field-issues) -- When a column loads but stays blank
* [Fix Type Name Errors](/powersheet/guides/troubleshooting/fix-type-name-errors) -- When the type a column reads from is itself wrong

***

<LastReviewed date="2026-09-14" />