We have a database of 90K serial numbers, and I’m trying to design an app for users to submit their serial numbers for a rewards program. Users currently can add / submit the serial numbers, but there is no verification or redlining of the serial number to prevent duplicate submission. There is nothing to notify them of a submission error or typo.
I’m not sure how most efficiently this would be done, but I’m currently tinkering around within the Simple CRM template. FYI
Hi John,
You can create a user-specific column to store the user’s input in a field, then make a relation from that field to the existing serial number column to verify that it has not existed in your database.
If the relation is empty, you let them submit and vice versa.
He has a database of 90,000 serials. Glide does not support this many rows.
Ok I have a similar issue as well but the serial numbers need to reference a brand name first and then check that brands serial numbers. Once the brand has been identified and then the serial number is found, the details of the product related to that serial number is then auto-filled for the user. Which is a nice feature. But if another user has already inputted the same brand and serial, i want it to recognise that that serial number has already been used and won’t autofill the details of the product. It will also trigger an alert to the user that the serial number is already “claimed”. They then have the opportunity of a few different options. To Dispute the Serial number as claimed. To prove that the system is wrong, the user is given the option to upload a receipt and photos of the product to prove they now own that product. Another option is to trigger the support ticket to investigate. From there the third party CRM can take over.
The main thing i’m interested in is the ability to identify that a serial number has already been claimed.