Discount Capped at 50%
This column validation uses a SharePoint formula to keep a discount rate from going above 50%. Applied as column validation, it checks the value the moment someone saves the item and blocks entries that do not pass.
How It Works
- What it does: Blocks the save if the Discount is above 50%.
- If it passes: Discount is 50% or less, so the item saves.
- If it fails: SharePoint stops the save and shows your message, for example: Discount cannot be more than 50%.
Common Use Cases
- Cap discounts within policy
- Preventing over-discounting
- Guardrails on pricing
- Approval-free discount limits
Details
- Formula Type: Column Validation
- Formula Category: Numbers & Money
Required Columns
| Display name | Column type |
|---|---|
| Discount | Number |
Prerequisites
- Create the column the formula reads: Discount
- Add or edit a few items so there is data for the formula to work with
How to Apply the Formula
- Open the column you want to validate (Edit column, then More options)
- Expand Column validation
- Paste the formula below into the Formula box
- Add a user message that explains the rule, so people know why an entry was blocked
- Save. From now on, new or edited entries must pass the rule
Formula (Copy and Paste)
=[Discount]<=0.5Common Questions About Discount Capped at 50% Formula
What does this formula do?
Cap a rate. It runs as column validation, so it checks the value when the item is saved and blocks entries that do not pass.
Which columns do I need to set this up?
You need: Discount (Number). The formula reads these to produce its result.
Will it check items that are already in the list?
No. Validation applies only to new or edited entries. Existing items are not re-checked when you add the rule.
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.
