Forum Discussion

SSNJeffP's avatar
SSNJeffP
Qrew Captain
8 months ago

Failed to check for record conflicts (New Forms)

I updated a form to the new version, and some users keep getting this error when trying to edit and save.  I was able to reproduce it, but I can't find any reason for it.

I've carefully gone over all of the form rules and there don't seem to be any conflicts.

Has anyone run into this and successfully solved it?

3 Replies

  • I believe what a record conflict means is that two people are editing the same record at the same time or one person is editing the same record on two different browser tabs at the same time and the system is getting confused as to which data is correct.

    This can happen when the first user calls up a record in adult mode and then while they are still sitting in Ed mode, a second user goes into the system updates that same record and saves it. 

    Quickbase is supposed to have built-in conflict resolution to lead the user through the process to determine which is the correct value for each field, field by field. However, I don't know what that message actually is because I've never seen it before.  It seems to be warning you that there is a conflict to be resolved, but the process to help you walk through and see which fields have conflicting value values is not working.

    • SSNJeffP's avatar
      SSNJeffP
      Qrew Captain

      Possibly,   even if I duplicate the record I end up with the same error,  but this only occurs on the new forms.  If I switch back to the legacy form it behaves as expected.    You do make me wonder if maybe a pipeline made an edit though and that is what is conflicting.

      • MikeTamoush's avatar
        MikeTamoush
        Qrew Elite

        Did you ever resolve this? I am getting this error but only for a single user. He gets this error only on mobile devices, but on multiple devices. And this error occurs any time uploading a file. Every record, any table. He simply cannot upload a file from a mobile device. No other users are reporting an issue and it works for me.

        Also, seems to happen on both new and legacy forms for this user, but only on mobile.