Datatable validation error - one or more cells contain invalid data

Forms SharePoint Online
1

As of this morning, we are getting a validation error like the one below when trying to save any form with a datatable. Is anyone else having this problem?

image

The datatable has no restrictions on data entered and no custom validation code. It doesn't depend on the column type (even happens when the datatable has no columns).

It was working on Friday, but stopped sometime over the weekend or this morning.

2

We're seeing the same issue on a form in production. I have no idea where the error is coming from — I've spent quite a while trying to debug it but couldn't find anything useful. The browser console doesn't show anything related to the validation either, and nothing was changed on our side recently. Can anyone help us out?

example
example1945×1355 132 KB

3

I ran into the same regression today (May 18). After inspecting the live Vue components in the browser, I found the root cause and a working workaround.

Root cause

A recently added validator named dataTableUnsavedRowValidator is attached to every DataTable. Its source (decoded from the minified bundle) is:

class eE {
    constructor(dataTable, errorMessage) {
        this._dataTable = dataTable;
        this.error = errorMessage;
    }
    validate() {
        return this._dataTable.isValid;
    }
    get name() {
        return "dataTableUnsavedRowValidator";
    }
}

The problem: this._dataTable.isValid is not a defined property on the fd-datatable Vue component — it isn't in data, computed, methods, or anywhere on the prototype chain. So validate() always returns undefined (falsy), which makes Plumsail report "One or more cells contain invalid data." even when every cell is perfectly valid.

I confirmed this on a live form: 4 rows of clean data, every row's hasErrors === false, dirty === false, no .k-invalid DOM nodes — yet validation fails. Calling dt.validate() returns false. After overriding the validator's validate() to return true, validation passes and saving works.

Workaround

Add this to your form's JavaScript. It finds the broken validator on the DataTable control after the form renders and replaces its validate() with one that returns true. Multiple setTimeout calls handle the fact that the validator is attached asynchronously.

fd.spRendered(function () {
    function patchDataTableValidator(controlName) {
        var dt = fd.control(controlName);
        if (!dt || !dt.validators) return;
        for (var i = 0; i < dt.validators.length; i++) {
            var v = dt.validators[i];
            if (v && v.name === 'dataTableUnsavedRowValidator' && !v._patched) {
                v.validate = function () { return true; };
                v._patched = true;
            }
        }
    }

    // Repeat for every DataTable control on the form
    ['DataTable1'].forEach(function (name) {
        setTimeout(function () { patchDataTableValidator(name); }, 300);
        setTimeout(function () { patchDataTableValidator(name); }, 1500);
        setTimeout(function () { patchDataTableValidator(name); }, 3000);
    });
});

If you have multiple DataTables on a form, add their internal names to the array (e.g. ['DataTable1', 'DataTable2']).

Caveats

  • This disables the "unsaved row" check entirely. If a user starts editing a row inline and clicks Save without committing the edit, the form will now save anyway. In our setup that's an acceptable trade-off — the original validator was a no-op for properly committed data and a blocker for everything else.
  • If you need the unsaved-row check, you could instead patch validate() to check widget._editContainer or widget.editable directly, but I haven't tested that path.

Tested on Plumsail Forms for SharePoint Online. Hope this unblocks people until Plumsail ships a fix.

4

I think there might be a fix in place because some unpatched forms are working now.

5

Thank you for this workaround. I think there is now a fix in place, so I haven't had much chance to try it, but I really appreciate you responding so fast and with so much detail.

6

Everyone, thank you for the report! The issue has been identified and should be fixed by now - try clearing browser's cache and see for yourself.

If you still experience the issue - let us know!