Boxed Field Section (Form Configuration)
Overview
- Groups the key fields into one clearly labeled section
- Keeps the most important details together and easy to find
- Built with the body section configuration, so it is simple and stable
- Any field left out is automatically added to the section
- Applied as form-configuration JSON in the body, so it changes nothing about the data
- Works on any list form, and the field set is easy to change
Common Use Cases
- Quick-entry forms
- Forms with a few critical fields
- Summary or key-detail blocks
- Approval forms
- Asset or record forms
- Any form needing a focused field group
How to Apply JSON Formatting
1. Open the list, then open any item to show its form.
2. At the top of the form, expand the Edit form (pencil) icon and choose Configure layout.
3. In the Apply formatting to dropdown, choose Body.
4. Paste the JSON below into the box, preview, and click Save.
JSON Code – Select, Copy and Paste
{
"sections": [
{
"displayname": "Key Details",
"fields": [
"Title",
"Category",
"Priority",
"Owner",
"Needed By"
]
}
]
}Common Questions About the Boxed Field Section
What is the Boxed Field Section built with?
It is built with a standard Microsoft List (SharePoint list) and form-configuration JSON applied to the form body. There is no custom development, no SPFx solution, and no third-party tools. It is the kind of clean, maintainable formatting Greg Zelfond builds for teams that want focused forms without ongoing development overhead.
How is this different from Grouped Form Sections?
Grouped Form Sections splits a form into several labeled groups. The Boxed Field Section uses a single, focused section to keep the most important fields together as one tidy block, which suits shorter or key-detail forms.
Does this design use any custom development or third-party tools?
No. It uses only out-of-the-box SharePoint form configuration, which Microsoft supports natively. That keeps it stable and easy to maintain, and nothing breaks when SharePoint is updated. Out-of-the-box is the only way Greg builds, so you can own and extend the design yourself for years.
If LookBook 365 is code-free and out-of-the-box, why does this example include JSON?
Because SharePoint formatting JSON is not custom code – it is a native configuration feature built into lists and libraries. It is declarative: it only describes how an existing form looks, and cannot run scripts, reach external services, or change your data. Nothing is deployed and nothing breaks when Microsoft updates SharePoint, and you can edit or remove it anytime. That is why LookBook 365 treats it as out-of-the-box and low risk.
Can I choose which fields go in the box?
Yes. You list the fields for the section in the JSON, so you decide exactly which ones appear in the block. Any field you do not list is simply added to the section automatically.
Can Greg build form formatting like this for our team?
Yes – this is exactly the kind of work Greg Zelfond does. As an independent SharePoint consultant and Microsoft MVP, he designs out-of-the-box list and library form formatting like this so your team can read and maintain it without a developer. Reach out through the contact page to talk about your forms.
