• Resolved siaccslv

    (@siaccslv)


    Hi Forminator Team,

    I am experiencing a critical data loss issue with the Google Sheets integration when processing long numeric strings. Specifically, I am dealing with national Cadastral numbers which are 17 digits long.

    The Technical Issue: When Forminator sends these numeric strings to Google Sheets, they are interpreted as integers (even though they are added as text fields and not numeric fields in forminator form). Because Google Sheets follows the IEEE 754 standard (64-bit floating point), it loses precision after the 15th digit, replacing subsequent numbers with zeros (e.g., 12329082498234188 becomes 12329082498234100).

    Reference to a Previous Ticket: I am aware of a similar ticket regarding this issue: https://ww.wp.xz.cn/support/topic/forminator-entries-in-google-sheet-are-not-getting-populated-in-the-correct-form/

    In that case, the support team suggested: “add any – even just one, at start or end – non-digit character to the voucher code.”

    Why this workaround is NOT applicable here: Unlike voucher codes, these are official, state-assigned legal identifiers used in company registration documents. I cannot freely interpret or modify these numbers by adding non-digit characters, as it would invalidate the legal integrity of the documents and the registration process. The data must remain purely numeric and exactly as entered by the user.

    Proposed Solution: Could you please add an option in the Google Sheets integration settings to “Force Text Format” for specific fields?

    Technically, this can be achieved by allowing a toggle that prepends a single quote (') to the value during the API call. This is the standard way to force Google Sheets to treat a cell as “Plain Text,” preserving every digit exactly as sent.

    This would be a massive improvement for any user dealing with:

    • National ID numbers / Cadastral codes
    • IBANs that are purely numeric in some regions
    • Long serial numbers for inventory

    I hope you can consider this for your development roadmap, as it would solve a persistent limitation of the current integration.

    Until such a feature is implemented, is there any filter or hook I could use to programmatically prepend the apostrophe to these specific fields before they are dispatched to the Google Sheets integration?

    Best regards,
    Elvijs

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter siaccslv

    (@siaccslv)

    Hi,

    I have further investigated how Forminator handles different field types, and I noticed that you already use the single quote (') prefix for Phone fields to preserve the + sign and prevent Google Sheets from treating it as a formula.

    This confirms that the ‘Force Text’ logic is already implemented within the plugin’s core, but it is currently limited to specific field types.

    My request is to extend this existing functionality to standard Text and Calculation fields. As mentioned, national legal identifiers (like the 17-digit codes I am processing) suffer from the exact same data corruption as phone numbers if they are not prepended with an apostrophe. Since the logic is already part of the plugin for phone numbers, could you provide a filter or an option to enable this ‘Plain Text’ force for other numeric-only text fields?

    This would ensure data integrity for legal codes, IBANs, and long serial numbers.

    Best regards,

    Elvijs

    • This reply was modified 3 months, 4 weeks ago by siaccslv.
    Plugin Support Imran – WPMU DEV Support

    (@wpmudev-support9)

    Hello @siaccslv,

    Thank you for sharing your detailed request!

    I checked, and it turns out we already have a similar feature request in our system. To ensure it gets noticed in the development team, I’m including the link internally. While I can’t give a specific timeline right now, feel free to keep an eye on the changelogs here: https://ww.wp.xz.cn/plugins/forminator/#developers.


    Kind Regards,
    Imran Khan

    Plugin Support Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    Hi @siaccslv,

    Since we haven’t heard from you for a while. I’ll mark this thread as resolved for now. Please feel free to re-open this thread if you need any further assistance.

    Kind Regards,

    Nithin

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.