Main design concern

[eajclement]

The fact that the formatting code is based on display names of columns is a major problem.

1. We always use multilingual display names. With this feature we must declare each column in every supported language. Painful !!!

2. If any team member renames a column, the formatting is broken.

The feature was nice, on paper, but sadly, not operationally usable :-(

The json code should use internal names

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 0f6aeedd-a76d-88b0-7ed5-93e20ac218bc
• Version Independent ID: 64315895-1103-d5f6-0195-9b5b61211132
• Content: Configure the list form
• Content Source: docs/declarative-customization/list-form-configuration.md
• Product: sharepoint
• GitHub Login: @VesaJuvonen
• Microsoft Alias: vesaj

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.