If an MCP-assisted GravityView edit changes a text label from 0123 to 123, inspect type handling before repairing the underlying form entries. A display setting that looks numeric may still be text. Converting it to a number can permanently remove meaningful leading zeros.
Check the scope of the published fix
GravityView 3.10.0, released October 29, fixes MCP View settings that converted numeric-looking text to numbers, including leading-zero labels. This concerns the affected setting path. It does not mean that every numeric ID or Number field should be changed to a string.
Use the current supported release and a staging View to reproduce the operation. Record the exact setting name, previous value, MCP operation, and resulting saved value. Avoid describing the problem simply as AI losing data when a specific configuration write can be identified.
Decide whether the value is text or quantity
A label such as Room 0123, an internal code, or a display prefix can require exact characters. A count, calculation input, or internal numeric object ID has a different contract. Choose the representation based on what the value means, not whether it contains only digits.
| Example |
Intended treatment |
What to compare |
| Display label 0123 |
Exact text |
Leading zero survives |
| Display text 001.20 |
Exact text if used as a code |
Zeros and punctuation survive |
| Internal View ID |
Follow the tool's documented ID type |
Correct object selected |
| Numeric quantity |
Follow the field's number contract |
Numeric meaning, not decorative padding |
Do not change form or entry IDs to make a label test pass. Those identifiers select objects and relationships. Also avoid applying number-display formatting as a repair for a text value that was already saved incorrectly; formatting cannot reliably reconstruct lost original characters.
Compare a text setting before and after an MCP-assisted edit without confusing labels with internal numeric IDs. Synthetic explanatory visual.
Compare the ordinary editor and MCP path
Create a disposable staging View with a harmless numeric-looking label. Save it through the normal editor, reopen the setting, and record the result. Then perform one narrowly scoped MCP edit to the same type of setting and inspect the stored configuration again through the supported interface.
Use the same input text for both paths. If the editor preserves 0123 but the MCP path saves 123, that narrows the issue to the tool operation or its handling of the setting. If both paths change it, review the field's intended type and any custom validation before attributing the problem to MCP.
Ask the assistant to modify only the named setting and report the changed fields. Do not combine this test with moving search fields, replacing templates, or publishing a new View. A broad operation makes it harder to tell whether a label change was intended or incidental.
Inspect the saved result and public rendering
Reopen the View after saving rather than relying on the tool's success message. Compare the label character for character, including spaces, punctuation, and leading zeros. Then inspect the rendered label on the designated test page. A correct tool response is not proof that persistence and rendering agree.
Include a second label containing letters, such as A0123, as a control. That helps distinguish numeric coercion from general truncation or a template using a different setting. Keep all examples synthetic and avoid sending real entry data to an assistant for this configuration-only test.
For AI-created forms, the PDF-to-form parity review covers the broader mapping from source questions to fields. This narrower test concerns a View setting's round trip, not whether every form question was captured correctly.
Recover from the original value, not a guess
After updating the supported components, restore the intended text from a trustworthy pre-change record and rerun the bounded operation. If the original code is unknown, ask its owner. Padding every number to four digits can create plausible but incorrect labels.
Keep a before-and-after configuration record and verify that unrelated settings remain unchanged. HandL WP can investigate an MCP configuration regression with the operation name, versions, and synthetic fixture. A useful acceptance result shows the exact text surviving the editor, tool write, saved setting, and rendered View.
Reference and review date
Primary technical reference. Sources checked October 30, 2026. The proposed procedures and original diagrams are explanatory test aids, not claims of customer testing or measured improvements.