How to Ship CRM Fixes Without a Rebuild

Fix production issues in a configurable CRM — a broken calculated field, a missing image, clipped output — using configuration changes plus a targeted cache clear, without a code redeploy or a full rebuild. Use this guide for low-risk production corrections where a rebuild would be slow, riskier, and out of proportion to the change.

• [ ] Admin access to the CRM's entity/formula manager and its caching controls.
• [ ] The ability to reproduce the issue on a real record before and after the change.
• [ ] Knowledge of every caching layer in play (application cache, page cache, "used CSS" cache, CDN).
• [ ] A rollback plan — know the previous value of anything you change.

1. 1

   Confirm Config Fix

   Confirm the fix is configuration, not code. If the change lives in a formula, a field setting, a content limit, or a stored asset, you can likely ship it without a rebuild. If it needs new logic, stop and use your normal release path.

2. 2

   Key on Changed Attribute

   Fix a two-way calculated field by keying on the changed attribute. When a field must compute in both directions — enter a percentage and get the amount, or enter the amount and get the percentage — branch the formula on which attribute the user actually edited, so the field just touched drives the calculation and the linked totals stay correct:

3. 3

   Restore Missing Assets

   Root-cause a "missing" asset before restoring it. A blank placeholder often isn't a code bug. An automated media cleaner can trash images it thinks are unused because they're referenced only inside a custom HTML widget it can't parse — the references are invisible to it. Restore the assets from the cleaner's trash rather than re-uploading blind.

4. 4

   Constrain Content

   Constrain content to fit a fixed box. When text is clipped inside a fixed-height, overflow:hidden box, don't enlarge the box — shrink the content to fit it. Lower the character limit feeding the renderer, match the input counter to the new limit so authors see the real ceiling, and reduce the font size and line height so the trimmed text sits cleanly.

5. 5

   Save and Clear Caches

   Save, then clear only the caches that matter. After each change, save and clear the specific caches involved — application/formula cache for a field, page and "used CSS" cache for a front-end asset. Clearing the right cache is what makes a config change go live; a rebuild is not required.

6. 6

   Verify Live

   Verify live on a real record, both directions where relevant. Re-open the affected record in production and confirm the fix, including any inverse case (both directions of a two-way field, desktop and mobile for an asset).

   result = isAttributeChanged(percent)
     ? base * percent / 100
     : (amount / base) * 100

• The calculated field returns correct results from either input, with no change to related totals.
• The restored asset returns HTTP 200 and renders on desktop and mobile.
• The clipped text now fits fully, verified on a worst-case long value.
• No rebuild or redeploy was needed, and the change is live.

• [ ] Confirmed the fix is config-only before choosing this path.
• [ ] Previous values recorded for rollback.
• [ ] Every relevant cache layer identified and cleared.
• [ ] Two-way fields verified from both inputs with no collateral change.
• [ ] Restored assets confirmed 200 on desktop and mobile.
• [ ] Clipped-content fixes verified against a worst-case value.
• [ ] Author-facing limits/counters aligned with renderer limits.

• Automated "unused asset" cleaners are blind to anything referenced in raw HTML, scripts, or custom widgets — keep an allowlist of assets used that way, or you'll fight the same disappearance repeatedly.
• When a fix genuinely needs new logic, don't force it through config: that's the case for your normal reviewed, staged release.