Custom Fields & Mass Update is two related utilities: Custom Fields lets you add your own fields to records (customers, vendors, items, transactions); Mass Update lets you change a field across many records in one operation. Both are powerful, both are dangerous if used without thought.

How to get there #

Menu: Tools → Custom Fields & Mass Update
Direct URL pattern: https://yourdomain.com/?bizRt=bizuno/tools/customFields

Custom Fields #

What you can add #

• Text (short or long) — free-form notes.
• Number — integer or decimal, optional min/max.
• Date.
• Dropdown (single-select) — list of pre-defined values.
• Checkbox — yes/no flag.
• Multi-select — check multiple values.

Where you can add them #

• Customer record
• Vendor record
• Inventory item
• Sales documents (quote, order, invoice) — header and/or line
• Purchase documents (PO, bill) — header and/or line
• Journal entry header
• Employee record
• Project record

Creating a custom field #

1. Pick the Record Type (e.g., Inventory Item).
2. Click New Field.
3. Configure:
   • Label — what users see.
   • Field Type.
   • Default Value (optional).
   • Required — enforce on save.
   • Tab / Section — where it appears on the record.
   • Show in List — include as a column in the record list/search.
4. Save.

Where custom fields appear downstream #

• PhreeForm — available as data fields for reports and printed forms.
• Import Manager — column in the CSV template for the record type.
• Search / filters — custom fields marked “Show in List” become filterable.
• Mass Update — custom fields can be mass-updated like built-in fields.

Examples at Ridgeline Cycles #

• Customer.Rider Profile — dropdown: Commuter / Road / Gravel / MTB / Family.
• Customer.Height (cm) — number, for fit recommendations.
• Inventory.Frame Size — dropdown: XS / S / M / L / XL.
• Inventory.Build Style — dropdown: Stock / Custom / Service-Only.
• Sales Line.Warranty Months — number.
• Employee.Park Tool Certification — date (expiration).

Important: Think carefully before adding a custom field. Every field you add is a field someone needs to populate, train on, and keep current. If you can achieve the same outcome with a category, tag, or existing field, do that instead. “Custom field creep” is a real problem at six months in.

Mass Update #

What it is #

Mass Update lets you change one or more fields across many records at once. Useful for:

• Raising all prices in a category by 5%.
• Setting a new default salesperson on 80 customers at once.
• Tagging a batch of items with a new custom field value.
• Inactivating a list of old vendors.
• Changing tax codes on customers after a rule change.

Running a mass update #

1. Back up first (Tools → Export & Backup). Mass updates have no undo button.
2. Pick the Record Type.
3. Set Filters to select the records to affect (critical — double-check the count before proceeding).
4. Preview the selected records — Bizuno shows you exactly which rows will be updated.
5. Pick the Field to Update and the new Value. Multiple fields can be updated at once.
6. For numeric fields, pick Operation: Set / Add / Subtract / Multiply / Percent Change.
7. Click Validate. Bizuno shows affected count and a sample of before/after values.
8. Click Apply. The update runs and produces a change log.

Important: Triple-check your filter. The fastest way to damage a Bizuno install is a mass update with a filter that matched more records than you thought. “Raise price by 10% where Category = Accessories” accidentally matched bikes too because the filter logic was off. Preview — then preview again.

Price update example #

Goal: raise all apparel MSRP by 3% for the spring season.

1. Backup.
2. Record type: Inventory Item.
3. Filter: Category = “Apparel”, Status = Active.
4. Preview: 142 items matched. Visually confirm the list looks right.
5. Field: MSRP. Operation: Percent Change. Value: 3.
6. Validate: shows $29.99 → $30.89 for the first sample row.
7. Apply. Change log shows 142 rows updated.
8. Spot-check 5 random apparel SKUs in the UI.

Inactivation example #

Goal: inactivate vendors that haven’t had a PO in 3 years.

1. Backup.
2. Record type: Vendor.
3. Filter: Last PO Date < today − 3 years, Status = Active.
4. Preview: 23 vendors matched. Scan for anyone you want to keep (sometimes a legacy vendor still matters).
5. Field: Status. Value: Inactive.
6. Validate, Apply.

Change log #

Every mass update writes a log entry: who ran it, when, filter, field, count, before/after samples. Logs are retained per your data retention policy (Admin settings). Logs are your audit trail.

Tips for Ridgeline Cycles #

• Make custom fields count. Before adding one, ask: will I report on this? filter on this? use it as a merge token? If not, it’s probably just a note — use the Description field instead.
• Never run a mass update without backing up first — no matter how small the affected set seems.
• When raising prices, keep the change log PDF next to the backup. If a customer disputes a price change later, you’ll want the evidence.
• For recurring mass updates (e.g., quarterly price refresh), save the filter as a named report or stash the filter criteria in a note — faster and less error-prone next time.

Where to go next #

• Import Manager — for bulk changes, CSV-based is often safer than mass update.
• PhreeForm — surface your custom fields in reports.
• Export & Backup — always first.