ChyanneEyde
5 years agoQrew Trainee
Rich text field button with "unsupported content"
Hello! I have a Rich text field called "Go to Next Tab" that is a button on a form. When clicked, it saves the record and leads the user to a second tab. It's been working perfectly for my use for months, and still works, but a message now appears, "This field includes unsupported content. We support the Quickbase formula syntax, as well as limited HTML. You can use JavaScript on code pages only." It goes on to say that "formulas with unsupported content may cease working without notice."
In an effort to avoid my very useful field from ceasing to work without notice, I am trying to get it into a form that is permissible. I could use some advice. I do have JS in a code page and the HTML tag I use, an a tag, appears to be in the list of HTML tags available for text fields. I tried so reconfigure a bit, but still get the message. Can anyone point out where I am breaking with QB guidance? I am sure I am overlooking something and would love another set of eyes on it. My field's formula is below. (For additional context, I originally created the field with inspiration from this QB community post. )
In the formula, I reference two variables and two code pages:
[customButtonScript1]
&"SaveAndNextTab.js"
&[customButtonScript2]
&"SaveandNextTabStyle.html"
Below is the content of each variable and code page:
customButtonScript1: <a href='javascript:($.getScript("https://octo.quickbase.com/db/bg8rdt9ai?a=dbpage&pagename=
SaveAndNextTab,js:
var nextTabLink=$("li.ui-tabs-active").next("[style!='display:none']").children("a");
$("#saveAndKeepWorkingMenuOption").click();
var noErrorDialog=$('#qbDialog').length==0;
if( noErrorDialog ){
$(nextTabLink).click();
location.assign('#navTop');
};
customButtonScript2: "));void(0);
SaveandNextTabStyle.html: 'class='Vibrant' style='background:#3399CC; border-radius: 5px; padding:8px 16px; text-decoration:none; color:#ffffff; display:inline-block; font-size:14px; text-align:center; white-space:nowrap'>Next</a>
When clicked, the button produces ($.getScript("https://octo.quickbase.com/db/bg8rdt9ai?a=dbpage&pagename=SaveAndNextTab.js"));void(0);
------------------------------
Chyanne
------------------------------
In an effort to avoid my very useful field from ceasing to work without notice, I am trying to get it into a form that is permissible. I could use some advice. I do have JS in a code page and the HTML tag I use, an a tag, appears to be in the list of HTML tags available for text fields. I tried so reconfigure a bit, but still get the message. Can anyone point out where I am breaking with QB guidance? I am sure I am overlooking something and would love another set of eyes on it. My field's formula is below. (For additional context, I originally created the field with inspiration from this QB community post. )
In the formula, I reference two variables and two code pages:
[customButtonScript1]
&"SaveAndNextTab.js"
&[customButtonScript2]
&"SaveandNextTabStyle.html"
Below is the content of each variable and code page:
customButtonScript1: <a href='javascript:($.getScript("https://octo.quickbase.com/db/bg8rdt9ai?a=dbpage&pagename=
SaveAndNextTab,js:
var nextTabLink=$("li.ui-tabs-active").next("[style!='display:none']").children("a");
$("#saveAndKeepWorkingMenuOption").click();
var noErrorDialog=$('#qbDialog').length==0;
if( noErrorDialog ){
$(nextTabLink).click();
location.assign('#navTop');
};
customButtonScript2: "));void(0);
SaveandNextTabStyle.html: 'class='Vibrant' style='background:#3399CC; border-radius: 5px; padding:8px 16px; text-decoration:none; color:#ffffff; display:inline-block; font-size:14px; text-align:center; white-space:nowrap'>Next</a>
When clicked, the button produces ($.getScript("https://octo.quickbase.com/db/bg8rdt9ai?a=dbpage&pagename=SaveAndNextTab.js"));void(0);
------------------------------
Chyanne
------------------------------