Disable popup that reads ""Save this record?
I understand that overriding the safety measures that QB has put in place is not a good idea but I feel there are always exceptions to the rules. I have a table in which I have fields that the user i...
Forum Discussion
New to this and seeing something similar, I want a form to hold temp values until we have an invoice that is suitable, when I update fields we get a message box asking to save so all values are lost.
Where should the code "function ConfirmLinkAway(){}" be stored? In the table, form, code page and how should it be called?
Where should the code "function ConfirmLinkAway(){}" be stored? In the table, form, code page and how should it be called?
Script is saved in code pages and accessed from you QuickBase pages using a script injection technique such as IOL. You can read about the IOL technique here:
https://haversineconsulting.quickbase.com/db/bgcwm2m4g?a=dr&rid=294
By placing this code
She Stoops to Conquer
Beyond that ask a new question concerning your specific need and context.
https://haversineconsulting.quickbase.com/db/bgcwm2m4g?a=dr&rid=294
By placing this code
function ConfirmLinkAway(){}in you script you are redefining QuickBase's authored function named ConfirmLinkAway to do nothing. It is a little know fact that you can redefine any function even those authored by QuickBase. In general redefining functions is not a good idea but we are in the world of workarounds here. This situation reminds me of this play:She Stoops to Conquer
Beyond that ask a new question concerning your specific need and context.