Added a new feature in Custom formatter for making fields readonly #10168
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Category
What's in this Pull Request?
🎯 Add documentation for Custom Formatter Read-Only Fields in Microsoft Lists
📝 Description:
This PR introduces detailed documentation for the new Custom Formatter for Read-Only Fields feature in Microsoft Lists. The formatter allows fields to appear as read-only in various form views — enhancing usability for AI-generated content and preventing accidental edits.
✅ Key Highlights:
Introduction and Purpose: Explains the need for read-only fields, especially in AI-driven list item creation.
Field Settings: Defines name and readonly properties for easy configuration.
Behavior Breakdown: Details how the formatter behaves across New Item, Edit Form, and Edit All modes.
Example Use Cases: Illustrates practical scenarios like CRM bot-generated tickets.
📌 Why It Matters:
Enables users to view essential data without the risk of unintentional modifications.
Supports AI and automation scenarios by protecting critical fields.