JavaScript – Custom Branding Change in June Release
JavaScript – Custom Branding Change in June Release
Earlier this year we announced some upcoming changes to how Quickbase will handle custom code (like JavaScript) when it is placed outside of code pages. Our first change took place in April 2021 and now our second phase that will affect Javascript in Custom Branding will take place in June 2021 during our monthly release. You can learn more about why we need to make these changes, when each specific change will happen, and what you can do to prepare in our blog post.
As of 06/13/2021, app builders will no longer be able to insert or edit content (like JavaScript) that is not supported in Custom Branding at the realm or app level. This means builders will not be able to save changes to Custom Branding that contains content like Javascript. Instead, builders will receive an error message warning them that content that is not supported in Custom Branding has been detected, and changes won’t be saved. After 06/13/2021, builders will only be able to save Custom Branding once any unsupported content is removed.
If you are an Account Admin, you can access the Inserted JavaScript Usage app to see if we detected any realm branding, app(s), table(s), and field(s) that contain JavaScript in your account. If you do not have access to the app, your Account Admin can help you to identify where your applications contain Javascript in your account. To see exceptions that will be impacted by the June release, look for Exceptions with the value “5. Found in app branding” or “6. Found in realm branding” in the Reason field. For more information on what’s changing in the June release, check out our release notes page.
If you have questions or need help, you can reach out to our Care team by submitting a support case.
*With this series of changes, we will not intentionally disable any existing solutions that leverage inserted JavaScript. However, it is impossible for us to test inserted JavaScript as we make changes to the Quickbase platform. A routine upgrade to an open-source library, a change to styling, or a change to our document object model (DOM) may cause these custom solutions to break without warning. This has always been a risk of leveraging such unsupported techniques. However, as we progress with projects like the UI Refresh in 2021 and beyond, these kinds of changes will become more frequent. And if a solution stops working for one of these reasons after the area has been closed, app builders will not be able to edit the JavaScript to fix it.