Short answer: The report usually can't handle a field whose type changed or a sort on a particular field. Remove that field or sort, save the report, and reopen it.
Why it happens
- A field's data type changed, for example from currency to number, and the report still references the old type. Changing a field type on a process that already has data can cause field version conflicts.
- The report sorts on a field it can't process.
- A platform bug after an update. Kissflow fixes these on its side.
How to fix it
-
If you recently changed a field's data type, edit the report and remove that field. Use the report search in the meantime.
-
Remove the sort on the problem field.
-
Open the report in Edit, save it, and open it again.
-
Try an incognito window to rule out cache.
-
If it still fails, collect evidence. Open your browser's developer tools, go to the Network tab, click Edit on the report and save what you see. Do the same with the Console tab.
-
Get your debug session key from your profile picture > My settings > API authentication > Debug session key > Show. See API authentication.
-
Send the evidence, the key and the report URL to Kissflow support.
See tabular reports.