Is there away to edit an error message?

  • 0
  • 1
  • Question
  • Updated 4 years ago
  • Answered
Example if I have a field that is filled out wrong, is there away I can edit the error message that pops up instead of the auto generated on?

Photo of Charles

Charles

  • 0 Points

Posted 4 years ago

  • 0
  • 1
Well no, but for that particular error message what I do is to rename my Unique field with long descriptive words which will work within the context of the other fixed text in the error message.

That error example is unusual in that you seem to have two fields needing to be unique.

For example you can rename the first field to be called [D1 Incident # has already been used]
Photo of Ⲇanom the ultimate (Dan Diebolt)

Ⲇanom the ultimate (Dan Diebolt), Champion

  • 30,264 Points 20k badge 2x thumb
>Well no ...

Well yes. Use the image onload technique and detect the a=FinishEditRecord page. I put a generic error message in the following pastie (see screenshot):

Custom Error Message - Enter Cartman
https://haversineconsulting.quickbase.com/db/bj369wh49?a=nwr

Pastie Database
https://haversineconsulting.quickbase.com/db/bgcwm2m4g?a=dr&rid=415

If you want to reword the error message you need to scrape some portion of the text out of the original message with some additional processing.
Photo of Charles

Charles

  • 0 Points
Thank you so much! That's awesome!
Photo of Ⲇanom the ultimate (Dan Diebolt)

Ⲇanom the ultimate (Dan Diebolt), Champion

  • 30,264 Points 20k badge 2x thumb
>That's awesome!

Well let's not loose track of the fact that this is a workaround hack. The whole purpose of using techniques like IOL  is to offer a temporary life cycle solution to a real problem or requirement that a users has. But in parallel we need to get QuickBase to implement a supported solution for adding user supplied JavaScript to pages and making customization that real users want. It is great to have native interfaces to control the product features but hard-coding specific features will never keep up with the broad range of features users want.

From QuickBase's development side of the aisle I am sure they are concerned over using these hacks for a variety of reasons including (1) adding user script that will eventually break when the pages are changed by QuickBase developers and (2)  for reasons of security. Now the IOL technique is secure because only an administrator can create the field [-]. If you are worried about a rouge administrator using IOL for evil your concern is misplaced as a rouge administrator has much easier way of messing with your data and users and hackers always use the least technical means to achieve their goals (despite what the technical press may say).

https://quickbase.uservoice.com/
Photo of Tribs

Tribs

  • 20 Points
Hi Dan, I want to use this technique but I get a popup message for the duplicate error instead of the Orange bar. do you know why there would be a difference in behavior and how to stop the popup so I can use custom messages.