Require Detail for ‘Other’
This list validation uses a SharePoint formula to require a detail field to be filled in when the category is Other. Applied as list validation, it compares the columns when the item is saved and blocks the entry if the rule is not met.
How It Works
- What it does: When Category is Other, requires the Details field to be filled in before the item can save.
- If it passes: Either Category is not Other, or it is and Details has text, so the item saves.
- If it fails: If Category is Other and Details is empty, the save is blocked and your message appears, for example: Please add details when Category is Other.
Common Use Cases
- Forcing an explanation for Other
- Complete categorization
- Better data capture
- Conditional required fields
Details
- Formula Type: List Validation
- Formula Category: Text & Names
Required Columns
| Display name | Column type |
|---|---|
| Category | Choice |
| Details | Single line of text |
Prerequisites
- Create the columns the formula reads: Category and Details
- Add or edit a few items so there is data for the formula to work with
How to Apply the Formula
- Go to List settings (or Library settings), then Validation settings
- Paste the formula below, which compares the columns
- Add a user message explaining the rule
- Save. New or edited items must satisfy the rule
Formula
=IF([Category]="Other",LEN([Details])>0,TRUE)
Common Questions About Require Detail for ‘Other’ Formula
What does this formula do?
Conditional mandatory field. It runs as list validation, comparing the columns when the item is saved.
Which columns do I need to set this up?
You need: Category (Choice), Details (Single line of text). The formula reads these to produce its result.
Why use list validation instead of column validation?
List (or library) validation can compare several columns to each other in the same item, which column validation cannot do.
If LookBook 365 is code-free and out-of-the-box, why does this example use a formula?
A SharePoint formula is native, declarative configuration, not custom development. It only works with the item’s own fields and simple logic – it cannot run scripts, reach external services, or change other data, and nothing is deployed to your tenant. It keeps working through Microsoft updates. If you would rather not set this up yourself, this is exactly the kind of thing I configure for clients.
