> For the complete documentation index, see [llms.txt](https://codifi-fdm.gitbook.io/codifi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codifi-fdm.gitbook.io/codifi-docs/mobile-app/creating-records/ripple-for-field-crews.md). # Ripple from a Field Crew's Perspective You don't need to know how Ripple works to use it. But you should know what it looks like, why it sometimes fills fields in, and what to do if a calculated value looks wrong. This page is the field-crew angle on **Ripple**, Codifi's built-in formula engine. For the formula-authoring side of the same feature, see [Ripple in the Cross-Platform section](/codifi-docs/cross-platform-features/ripple.md). *** ## The FX icon Look for the **FX icon** next to a field's label. That icon means "this field is calculated by a formula." The value pre-fills (or updates as related fields change) automatically — you usually don't need to edit it. A few common patterns you'll see: | Pattern | What it does | | ------------------- | --------------------------------------------------------------------------------------------- | | **Auto-totals** | A "Total Depth" field that adds up horizon thicknesses as you fill them in. | | **Auto-area** | An "Area" field that multiplies Length × Width as soon as you enter both. | | **Inherited names** | A child Record's title that auto-builds from the parent's name (e.g., "Site 5 — Feature 02"). | | **Auto-UTM** | UTM coordinates that fill from a GPS capture without your re-entering them. | | **Smart defaults** | A "Status" field that defaults to "In Progress" when you first edit the Record. | *** ## Two flavors of FX field Calculated fields come in two flavors. The difference matters for what you can do as a crew member. ### Read-only calculated The field is **fully controlled by the formula**. You can't type into it; whatever the formula computes is the value. Use case: totals, areas, anything where the formula is authoritative. What to do if it looks wrong: **the formula is wrong, not the field**. Talk to your project manager — they need to fix the Composition. You can't override the value from the field. ### Editable with a smart default The field has a formula, but it's also editable. The formula **pre-fills** the field — but if you type something, your value wins. Use case: parent-name inheritance with possible overrides ("default to Site 5 — Feature 02, but let me rename if needed"), suggested status with override capacity. What to do if it looks wrong: just type the correct value. Your edit sticks. > **How to tell them apart:** read-only calculated fields are visually styled the same way as any read-only field (grayed out, not tappable for input). Editable-with-default fields look normal and accept typing. *** ## When Ripple does something unexpected Common surprises and what they mean: ### "I typed a value and then it disappeared / got overwritten." You probably typed into a **read-only calculated** field that briefly accepted input on touch but then reverted to the formula's output. The formula won. If you genuinely need to override that value, the field needs to become editable — that's a Composition change on the web side. Talk to your PM. ### "The auto-fill didn't fill — the field is still empty." The formula probably depends on a field that's still empty. Once you fill the dependency (e.g., the **Length** and **Width** that feed an **Area** calculation), the FX field updates. If both dependencies are filled and the FX field is still empty, something's off in the Composition. Note the affected field for your PM. ### "The auto-calculated total is wrong." Re-check the inputs that feed it. Most "wrong total" cases turn out to be a misentered input (e.g., a soil horizon's top depth typed as the bottom depth by accident). If inputs are right and the total is genuinely wrong, that's a formula error in the Composition. Note the Record's title, the inputs, and the expected vs. actual total for your PM. ### "Visibility rules are showing the wrong fields." Codifi can show/hide fields based on other field values (see [Conditional Visibility](/codifi-docs/cross-platform-features/conditional-visibility.md)). If a field is appearing that shouldn't, or vice versa, check the field your Composition keys on. Usually it's a Yes/No or dropdown that needs to be set first. *** ## How to recognize Ripple at runtime Cues that you're looking at a Ripple-driven field: * **The FX icon** next to the label. * **A grayed-out input** that won't accept typing. * **A value that fills in automatically** when you fill related fields. * **A field that shows up suddenly** when you set another field to a certain value (that's visibility, not value computation — different flavor of Ripple). *** ## Ripple is local and offline Ripple runs on your iPad, not on the server. That means: * **Calculated fields work offline.** No connectivity required. * **Auto-fill happens immediately** as you edit, with no lag. * **Sync doesn't recompute** — what you saw on your iPad is what syncs to the server. (The server validates that the values are consistent, but doesn't override your captured values.) This is one of the reasons Codifi feels fast in the field — no round- trip to the server for every calculation. *** ## What's NOT Ripple A few things that LOOK like Ripple but aren't: * **Default values that aren't formulas.** Some fields have a static default value configured in the Composition (e.g., a Project type that defaults to "Survey"). These pre-fill but aren't computed — they're just defaults. * **Auto-numbering.** Record titles that auto-increment (STP-001, STP-002) come from a separate auto-numbering system. See [Record Auto-Numbering](/codifi-docs/mobile-app/mobile-project-settings/record-auto-numbering.md). * **Sync-time consistency checks.** When you sync, the server may notice and flag inconsistencies — that's validation, not Ripple computation. *** ## Common questions ### Can I learn to write Ripple formulas? You can — Ripple has a full reference under [Cross-Platform Features → Ripple](/codifi-docs/cross-platform-features/ripple.md). In practice, formula authoring is gated by the **Composer** role and happens on the web side. Most field crew members don't author formulas; they report issues to whoever does. ### If I disagree with how a formula calculated something, can I edit it? You can't change the formula from your iPad. If the field is **editable**, you can type your own value (which sticks unless the formula is the read-only kind). If it's **read-only**, your only option is to flag the issue with your project manager. ### How do I report a formula issue to my PM? Capture: the Project name, the Record's title, the field with the problem, what the formula computed, and what you expected. The PM will check the Composition. *** ## Related * [**Cross-Platform Features → Ripple**](/codifi-docs/cross-platform-features/ripple.md) — the formula authoring side, for Composition authors. * [**Calculated Fields**](/codifi-docs/cross-platform-features/calculated-fields.md) — the concept page that pairs with this one. * [**Conditional Visibility**](/codifi-docs/cross-platform-features/conditional-visibility.md) — show/hide rules, which are also Ripple under the hood. * [**Example 1**](/codifi-docs/mobile-app/creating-records/example-1-stps-on-a-transect.md) and [**Example 2**](/codifi-docs/mobile-app/creating-records/example-2-utah-site-form.md) — Ripple in real workflows.